Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10520f905176dbf49b40f50983c7b6c2d949f893b105524f70b4fddd934aca78

Tx prefix hash: c65c54640d8583e4a5dc95e7a01783a428b7f10e3622fcfb1a626645e90fba5b
Tx public key: 737bd1c36b9654d0b2c36d84505eef5506b1811129d34ab8cf744b8f0774c938
Timestamp: 1739272116 Timestamp [UCT]: 2025-02-11 11:08:36 Age [y:d:h:m:s]: 00:356:03:21:10
Block: 1216899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252211 RingCT/type: yes/0
Extra: 01737bd1c36b9654d0b2c36d84505eef5506b1811129d34ab8cf744b8f0774c93802110000001a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4877e4ba0a520e136fa558d90edfe6bc706ca2afb2595bd36418d67b36b9ae22 0.600000000000 1703708 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": 1216909, "vin": [ { "gen": { "height": 1216899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4877e4ba0a520e136fa558d90edfe6bc706ca2afb2595bd36418d67b36b9ae22" } } ], "extra": [ 1, 115, 123, 209, 195, 107, 150, 84, 208, 178, 195, 109, 132, 80, 94, 239, 85, 6, 177, 129, 17, 41, 211, 74, 184, 207, 116, 75, 143, 7, 116, 201, 56, 2, 17, 0, 0, 0, 26, 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