Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7df5859f8ba5c6ea657ad09c92b9016f3364190483dbd6c6619d93aef729b595

Tx prefix hash: 454fb81ce77162914130d74836ae3169530d77c142aa315da8d847ec1750fe7d
Tx public key: 99d0b90da0c8ab38cbf9860ab2877e702262bc574ef668e9d4dcd2ed5203c1f1
Timestamp: 1721003892 Timestamp [UCT]: 2024-07-15 00:38:12 Age [y:d:h:m:s]: 00:269:02:51:41
Block: 1065891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192258 RingCT/type: yes/0
Extra: 0199d0b90da0c8ab38cbf9860ab2877e702262bc574ef668e9d4dcd2ed5203c1f102110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b84137bcb1e27812bde0d20be9a2a77dd1be4ef88c56b3c1e3fdf5b4705c1f3 0.600000000000 1536460 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": 1065901, "vin": [ { "gen": { "height": 1065891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b84137bcb1e27812bde0d20be9a2a77dd1be4ef88c56b3c1e3fdf5b4705c1f3" } } ], "extra": [ 1, 153, 208, 185, 13, 160, 200, 171, 56, 203, 249, 134, 10, 178, 135, 126, 112, 34, 98, 188, 87, 78, 246, 104, 233, 212, 220, 210, 237, 82, 3, 193, 241, 2, 17, 0, 0, 0, 12, 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