Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc3677d78cbfbb36cf63d0340b39cc8a3de16479ed1d9b93d13ad708f1a61bf6

Tx prefix hash: a7358667fb3b8deabc21d4519679c8b7cd954c2a81cfc3f6784617a2bd1da3f4
Tx public key: 39f60d6757e1dac2c2c292444b121894ed21fbd3318195338fb48d1db02cec74
Timestamp: 1694244968 Timestamp [UCT]: 2023-09-09 07:36:08 Age [y:d:h:m:s]: 01:170:13:37:34
Block: 844218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382985 RingCT/type: yes/0
Extra: 0139f60d6757e1dac2c2c292444b121894ed21fbd3318195338fb48d1db02cec7402110000000e75e3f0e9000000000000000000

1 output(s) for total of 0.978938434000 dcy

stealth address amount amount idx
00: d45779bd70695057572d2a2025ae731732cd51cfab46f9ea970e4b777d36fa56 0.978938434000 1297514 of 0

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": 844228, "vin": [ { "gen": { "height": 844218 } } ], "vout": [ { "amount": 978938434, "target": { "key": "d45779bd70695057572d2a2025ae731732cd51cfab46f9ea970e4b777d36fa56" } } ], "extra": [ 1, 57, 246, 13, 103, 87, 225, 218, 194, 194, 194, 146, 68, 75, 18, 24, 148, 237, 33, 251, 211, 49, 129, 149, 51, 143, 180, 141, 29, 176, 44, 236, 116, 2, 17, 0, 0, 0, 14, 117, 227, 240, 233, 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