Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95d9992e7711a1d39376811306c14cfa5e4096d841c7fc78797d320366729e23

Tx prefix hash: 55ab2e876196468668f20c6ed9d0f7ecf81201e38b7b42810774e6fb914f7ddd
Tx public key: 2124ec4f588984092a432ed686f8e85ed714b3e7df089a890b8acab6f288046b
Timestamp: 1708821811 Timestamp [UCT]: 2024-02-25 00:43:31 Age [y:d:h:m:s]: 01:257:21:06:08
Block: 964888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443036 RingCT/type: yes/0
Extra: 012124ec4f588984092a432ed686f8e85ed714b3e7df089a890b8acab6f288046b02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0a1991fdc6f9331d42e14df80e9ea9a4ddacf42d8ea34e560b4b95ffb0390bb 0.600000000000 1424631 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": 964898, "vin": [ { "gen": { "height": 964888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0a1991fdc6f9331d42e14df80e9ea9a4ddacf42d8ea34e560b4b95ffb0390bb" } } ], "extra": [ 1, 33, 36, 236, 79, 88, 137, 132, 9, 42, 67, 46, 214, 134, 248, 232, 94, 215, 20, 179, 231, 223, 8, 154, 137, 11, 138, 202, 182, 242, 136, 4, 107, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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