Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 156d5879a8f64bb372ed841104c3d71c8dc26b75407a16c4fdfbdcec3150f3c7

Tx prefix hash: 3f40752441d2a80c351e37ee6bbc9f2db4295a0dc2207723b2c85dab8c84a75e
Tx public key: 8e8c9c65bd048b42b0c02efa62987fa3b9632caed97adb31105a2d1b6b8fc9a2
Timestamp: 1713656156 Timestamp [UCT]: 2024-04-20 23:35:56 Age [y:d:h:m:s]: 01:193:22:10:43
Block: 1004954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397250 RingCT/type: yes/0
Extra: 018e8c9c65bd048b42b0c02efa62987fa3b9632caed97adb31105a2d1b6b8fc9a20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efb840ccffb3fbcff6bf90f1be86cb18e4fe39b032eec2f18669b4ab06a37dbd 0.600000000000 1465528 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": 1004964, "vin": [ { "gen": { "height": 1004954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efb840ccffb3fbcff6bf90f1be86cb18e4fe39b032eec2f18669b4ab06a37dbd" } } ], "extra": [ 1, 142, 140, 156, 101, 189, 4, 139, 66, 176, 192, 46, 250, 98, 152, 127, 163, 185, 99, 44, 174, 217, 122, 219, 49, 16, 90, 45, 27, 107, 143, 201, 162, 2, 17, 0, 0, 0, 1, 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