Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 123070735bc95c1278c8e661c691c39002c91a16162c9065e53f6bc1da6ab166

Tx prefix hash: d410c3e8aaedf37e91c684d7d53c7f32485fd5c15ba1789f1fcc40ec057836e3
Tx public key: bfbd8c3dd3c6440f4e116bd99d597569c90b2c6d1d49f361228025c266496150
Timestamp: 1731529774 Timestamp [UCT]: 2024-11-13 20:29:34 Age [y:d:h:m:s]: 01:006:08:17:56
Block: 1153055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262955 RingCT/type: yes/0
Extra: 01bfbd8c3dd3c6440f4e116bd99d597569c90b2c6d1d49f361228025c266496150021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11e9e7d5136483d90e6552c1cf3d877fdb66e235a066fa37cf9a6a5b531b1df9 0.600000000000 1638662 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": 1153065, "vin": [ { "gen": { "height": 1153055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11e9e7d5136483d90e6552c1cf3d877fdb66e235a066fa37cf9a6a5b531b1df9" } } ], "extra": [ 1, 191, 189, 140, 61, 211, 198, 68, 15, 78, 17, 107, 217, 157, 89, 117, 105, 201, 11, 44, 109, 29, 73, 243, 97, 34, 128, 37, 194, 102, 73, 97, 80, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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