Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d8fd11bda9a9665e90ebfca9b940366f2942f550221a7ed81a51499e3790cf5

Tx prefix hash: 3fea144d3dd083ac84f4616e92caf1c61ee5e63ae3b749b1aedacbcf2e3ee47c
Tx public key: 94e2c89b4c72a94094d40b960c46c144af44e059a041c22ae8205e6a32e22ca9
Timestamp: 1727062957 Timestamp [UCT]: 2024-09-23 03:42:37 Age [y:d:h:m:s]: 00:191:11:46:38
Block: 1116109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136675 RingCT/type: yes/0
Extra: 0194e2c89b4c72a94094d40b960c46c144af44e059a041c22ae8205e6a32e22ca9021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e920577ddd014cd1d1dfeebf54fb74b9f0f09d8f39cb87729408c13c329bc1e9 0.600000000000 1596480 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": 1116119, "vin": [ { "gen": { "height": 1116109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e920577ddd014cd1d1dfeebf54fb74b9f0f09d8f39cb87729408c13c329bc1e9" } } ], "extra": [ 1, 148, 226, 200, 155, 76, 114, 169, 64, 148, 212, 11, 150, 12, 70, 193, 68, 175, 68, 224, 89, 160, 65, 194, 42, 232, 32, 94, 106, 50, 226, 44, 169, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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