Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf9b4b254a49ee888dfd90c5011fb789d1afd8626b29e8d6d608ae7c6dba8388

Tx prefix hash: 641e21f61ac86555bcc57457f8842b9a8356714e911d21f5c26b4053a6385f0a
Tx public key: c92a14d369b31c0009bfc7befc34f1c611422af75a271d48f277eb5b7fd616fb
Timestamp: 1736766229 Timestamp [UCT]: 2025-01-13 11:03:49 Age [y:d:h:m:s]: 00:157:11:16:13
Block: 1196410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112227 RingCT/type: yes/0
Extra: 01c92a14d369b31c0009bfc7befc34f1c611422af75a271d48f277eb5b7fd616fb021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f57a432e2bce161d736d60f545d4d35a4a6c3eb6ae37884d5bfc710c4215ebf 0.600000000000 1683009 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": 1196420, "vin": [ { "gen": { "height": 1196410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f57a432e2bce161d736d60f545d4d35a4a6c3eb6ae37884d5bfc710c4215ebf" } } ], "extra": [ 1, 201, 42, 20, 211, 105, 179, 28, 0, 9, 191, 199, 190, 252, 52, 241, 198, 17, 66, 42, 247, 90, 39, 29, 72, 242, 119, 235, 91, 127, 214, 22, 251, 2, 17, 0, 0, 0, 4, 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