Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5744cab82b63fda42d7a6f26606deb48058cb3cbfae73285829f14291afb3a7d

Tx prefix hash: cd3cc05a00d26f27b6b0f03611bcdff05def128fb98fa456f9260aaff18aff30
Tx public key: ba9833fbbe46f5bdff63a99f3c1360d98ba2ecac798efebd10284a54a4fa23d3
Timestamp: 1649907882 Timestamp [UCT]: 2022-04-14 03:44:42 Age [y:d:h:m:s]: 02:255:10:12:52
Block: 479762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 702443 RingCT/type: yes/0
Extra: 01ba9833fbbe46f5bdff63a99f3c1360d98ba2ecac798efebd10284a54a4fa23d302110000000a2e6b1fd5000000000000000000

1 output(s) for total of 15.788816251000 dcy

stealth address amount amount idx
00: 06d74e703bb321a8259d8ad5928be3f1a7a5350cbcb4a40f215284296e52c5c9 15.788816251000 900717 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": 479772, "vin": [ { "gen": { "height": 479762 } } ], "vout": [ { "amount": 15788816251, "target": { "key": "06d74e703bb321a8259d8ad5928be3f1a7a5350cbcb4a40f215284296e52c5c9" } } ], "extra": [ 1, 186, 152, 51, 251, 190, 70, 245, 189, 255, 99, 169, 159, 60, 19, 96, 217, 139, 162, 236, 172, 121, 142, 254, 189, 16, 40, 74, 84, 164, 250, 35, 211, 2, 17, 0, 0, 0, 10, 46, 107, 31, 213, 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