Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0fe7175e288b2b21ca5d951d29c4c6f4cd28112837059fb12db50b91c54c131

Tx prefix hash: c90c78be7cf73d3dda61cf019b0d5436e1d9360fefcc14bd753b743a1f6df332
Tx public key: b515180d4559f9b75fe14e7f549e66ba024a1240e466574d70d0ad6e71182830
Timestamp: 1731425509 Timestamp [UCT]: 2024-11-12 15:31:49 Age [y:d:h:m:s]: 00:139:06:44:12
Block: 1152183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99370 RingCT/type: yes/0
Extra: 01b515180d4559f9b75fe14e7f549e66ba024a1240e466574d70d0ad6e71182830021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afd8c0ee01512ec59d2c0da6ed53093ed324ff863768022fd0c9e8c0101d76e4 0.600000000000 1637774 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": 1152193, "vin": [ { "gen": { "height": 1152183 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afd8c0ee01512ec59d2c0da6ed53093ed324ff863768022fd0c9e8c0101d76e4" } } ], "extra": [ 1, 181, 21, 24, 13, 69, 89, 249, 183, 95, 225, 78, 127, 84, 158, 102, 186, 2, 74, 18, 64, 228, 102, 87, 77, 112, 208, 173, 110, 113, 24, 40, 48, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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