Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c923e8aa97b519a82710f6931d4c9262d495f54f1787bf964e1fd33c00f2c2e8

Tx prefix hash: 5ec07d6bcbc9cda95f007e426f0b827fc69e730a2664123cd1153d43139059db
Tx public key: e91f1246e5e45c7a550ee7fd3ccc21c28d4dd1bbc98a6591786669a9c7bf0611
Timestamp: 1722102097 Timestamp [UCT]: 2024-07-27 17:41:37 Age [y:d:h:m:s]: 00:260:06:27:56
Block: 1074978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185949 RingCT/type: yes/0
Extra: 01e91f1246e5e45c7a550ee7fd3ccc21c28d4dd1bbc98a6591786669a9c7bf061102110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3629342c89aceddaafc29f68cd872ee1b27d1884695ff4cf53aada0bc99d2dcf 0.600000000000 1547497 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": 1074988, "vin": [ { "gen": { "height": 1074978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3629342c89aceddaafc29f68cd872ee1b27d1884695ff4cf53aada0bc99d2dcf" } } ], "extra": [ 1, 233, 31, 18, 70, 229, 228, 92, 122, 85, 14, 231, 253, 60, 204, 33, 194, 141, 77, 209, 187, 201, 138, 101, 145, 120, 102, 105, 169, 199, 191, 6, 17, 2, 17, 0, 0, 0, 10, 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