Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 575f0985bcf3472424184dc4f29fcd200d007f2adef41ba89ef44611451635b1

Tx prefix hash: 63d8ee5d4e32bc69caaccf38a372f8586e3b345f1a66ea043051d2ef93d0f5f2
Tx public key: b55978dc79d735f7cee1be11b7dd27fc724ea46e28b6372d338c20a27381f8ae
Timestamp: 1695612233 Timestamp [UCT]: 2023-09-25 03:23:53 Age [y:d:h:m:s]: 01:199:05:25:35
Block: 855560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403464 RingCT/type: yes/0
Extra: 01b55978dc79d735f7cee1be11b7dd27fc724ea46e28b6372d338c20a27381f8ae021100000001faf35c9c000000000000000000

1 output(s) for total of 0.897789679000 dcy

stealth address amount amount idx
00: 49bf5e25d0aadbcc3bac69620d37dbbfa44532e5fdf8251d4ae957033733cc39 0.897789679000 1309586 of 0

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": 855570, "vin": [ { "gen": { "height": 855560 } } ], "vout": [ { "amount": 897789679, "target": { "key": "49bf5e25d0aadbcc3bac69620d37dbbfa44532e5fdf8251d4ae957033733cc39" } } ], "extra": [ 1, 181, 89, 120, 220, 121, 215, 53, 247, 206, 225, 190, 17, 183, 221, 39, 252, 114, 78, 164, 110, 40, 182, 55, 45, 51, 140, 32, 162, 115, 129, 248, 174, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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