Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbcdb7489493b28283e8180c3558cfc4ebb572b4530914add3ab538e9ab5a0db

Tx prefix hash: b176f93b8586aecbdd7cead92c636b37bcd4261199ed89bce66764a0541612f4
Tx public key: 8d14bf7fd24970ce6d8b7f5c9fcaa600e750d2f2711193812c3d4250b5156041
Timestamp: 1736425112 Timestamp [UCT]: 2025-01-09 12:18:32 Age [y:d:h:m:s]: 00:302:13:05:10
Block: 1193591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213735 RingCT/type: yes/0
Extra: 018d14bf7fd24970ce6d8b7f5c9fcaa600e750d2f2711193812c3d4250b5156041021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0643d8a74e4439f49244d6bbd6b2f36e3f1c32a303aec25e3f45d2d90a8d9065 0.600000000000 1680154 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": 1193601, "vin": [ { "gen": { "height": 1193591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0643d8a74e4439f49244d6bbd6b2f36e3f1c32a303aec25e3f45d2d90a8d9065" } } ], "extra": [ 1, 141, 20, 191, 127, 210, 73, 112, 206, 109, 139, 127, 92, 159, 202, 166, 0, 231, 80, 210, 242, 113, 17, 147, 129, 44, 61, 66, 80, 181, 21, 96, 65, 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