Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21bc363d1ec41b0e83a798dc40e6b6d1a9ecceac1999f07ad894bf1c4a7318f9

Tx prefix hash: 49253b8a2e423f01670c776f65e38f09d64c9a6bf6b10581384569dc61cc3103
Tx public key: 0142e3d240418a8cb124eef2f9dccf868ffeb18229324ddec5c222bbf1be37b7
Timestamp: 1718598036 Timestamp [UCT]: 2024-06-17 04:20:36 Age [y:d:h:m:s]: 00:164:22:29:52
Block: 1045928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118047 RingCT/type: yes/0
Extra: 010142e3d240418a8cb124eef2f9dccf868ffeb18229324ddec5c222bbf1be37b70211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f729f2062976af0d7525c240ec1c939c1d750b8d1097884c1a3aac87b542ecf5 0.600000000000 1515645 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": 1045938, "vin": [ { "gen": { "height": 1045928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f729f2062976af0d7525c240ec1c939c1d750b8d1097884c1a3aac87b542ecf5" } } ], "extra": [ 1, 1, 66, 227, 210, 64, 65, 138, 140, 177, 36, 238, 242, 249, 220, 207, 134, 143, 254, 177, 130, 41, 50, 77, 222, 197, 194, 34, 187, 241, 190, 55, 183, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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