Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1836b9577b0ae6a2ff76e421372445b1ddf8e33a0a389c1e67dfe6a9f7c3c554

Tx prefix hash: eb57b5bd6de8e4e7f9111c1d497d91bc567f060a13b851fbbf82ab15783ef65b
Tx public key: be97b3ae65a9e92739ceed8f89cfb35d9b40691311766b3a56a631aba39abd4f
Timestamp: 1721525936 Timestamp [UCT]: 2024-07-21 01:38:56 Age [y:d:h:m:s]: 00:242:15:37:58
Block: 1070211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173347 RingCT/type: yes/0
Extra: 01be97b3ae65a9e92739ceed8f89cfb35d9b40691311766b3a56a631aba39abd4f02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef79025fbf405c6c27d65356fd9fbccc1c6a6fc188488daa5557f3dbe1087213 0.600000000000 1541948 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": 1070221, "vin": [ { "gen": { "height": 1070211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef79025fbf405c6c27d65356fd9fbccc1c6a6fc188488daa5557f3dbe1087213" } } ], "extra": [ 1, 190, 151, 179, 174, 101, 169, 233, 39, 57, 206, 237, 143, 137, 207, 179, 93, 155, 64, 105, 19, 17, 118, 107, 58, 86, 166, 49, 171, 163, 154, 189, 79, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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