Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54994c087fd48210e9a9e107285bd87a94ed4219fe07b7f1765e35815bb013d2

Tx prefix hash: 4a235f95bbb0ce90e63df8e322ea263d9bc9a3467e737238c688b21d5d76b49f
Tx public key: 40ec5428ffcb831e6b5bd53e5dc54f201d66f1ee1d24af9d8fa4ff16c5b7edf4
Timestamp: 1712382575 Timestamp [UCT]: 2024-04-06 05:49:35 Age [y:d:h:m:s]: 01:055:15:25:31
Block: 994369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300800 RingCT/type: yes/0
Extra: 0140ec5428ffcb831e6b5bd53e5dc54f201d66f1ee1d24af9d8fa4ff16c5b7edf402110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f64d5f5451e3b092fc699e21d4719f94f11f84d3dd319fdaae51692577114bfe 0.600000000000 1454771 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": 994379, "vin": [ { "gen": { "height": 994369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f64d5f5451e3b092fc699e21d4719f94f11f84d3dd319fdaae51692577114bfe" } } ], "extra": [ 1, 64, 236, 84, 40, 255, 203, 131, 30, 107, 91, 213, 62, 93, 197, 79, 32, 29, 102, 241, 238, 29, 36, 175, 157, 143, 164, 255, 22, 197, 183, 237, 244, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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