Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: cc64f2d0505e178c1d42db5379a9c340e2e5732c0bbffde3275620c8c9b4e5f0

Tx prefix hash: 94f831cec46d72d10b240fd4588006a1732479709d4c83d20b316a480ae7f8fe
Tx public key: 60fac4db47f043e53030a0ef3617ed218299b313980c61b85ae6194e7ce5c937
Timestamp: 1721462750 Timestamp [UCT]: 2024-07-20 08:05:50 Age [y:d:h:m:s]: 00:191:11:07:32
Block: 1069675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136751 RingCT/type: yes/0
Extra: 0160fac4db47f043e53030a0ef3617ed218299b313980c61b85ae6194e7ce5c9370211000000014385362a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ebc09eadcb43237e63735cf7b3dcf991f77d9c9b7b6b7c996cdd6cfcf5cee3e 0.600000000000 1541200 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1069685, "vin": [ { "gen": { "height": 1069675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ebc09eadcb43237e63735cf7b3dcf991f77d9c9b7b6b7c996cdd6cfcf5cee3e" } } ], "extra": [ 1, 96, 250, 196, 219, 71, 240, 67, 229, 48, 48, 160, 239, 54, 23, 237, 33, 130, 153, 179, 19, 152, 12, 97, 184, 90, 230, 25, 78, 124, 229, 201, 55, 2, 17, 0, 0, 0, 1, 67, 133, 54, 42, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8