Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80ed073c3304403d58a5bc03859caad47783072e1cfa44ab7f44a731ba8e1a8c

Tx prefix hash: b96ebbea17f4e1173ba77596cf8e463e8736223873237b735432800598f88f56
Tx public key: 6aa97736d0126c08694d9a2e88be2b7cb466ab7b8e09c7a5fbafbb81ed5617ee
Timestamp: 1709558388 Timestamp [UCT]: 2024-03-04 13:19:48 Age [y:d:h:m:s]: 00:326:07:25:58
Block: 970996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233524 RingCT/type: yes/0
Extra: 016aa97736d0126c08694d9a2e88be2b7cb466ab7b8e09c7a5fbafbb81ed5617ee0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2dda00a5b3ec5e312ed8d5026d001700590ec2dec192468a74a703516bbe4f3 0.600000000000 1430869 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": 971006, "vin": [ { "gen": { "height": 970996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2dda00a5b3ec5e312ed8d5026d001700590ec2dec192468a74a703516bbe4f3" } } ], "extra": [ 1, 106, 169, 119, 54, 208, 18, 108, 8, 105, 77, 154, 46, 136, 190, 43, 124, 180, 102, 171, 123, 142, 9, 199, 165, 251, 175, 187, 129, 237, 86, 23, 238, 2, 17, 0, 0, 0, 9, 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