Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 095d798aadfc40a6464db1fdcd1e4dd24267acf366bea59c6c62c4f188f29d7d

Tx prefix hash: cb1164bf42cabee6d2803bb3e6fc6bd6c160933ae54aeba87ef57b6c5901d34c
Tx public key: 13fde0ffeaa827cf32ea7bb1ae523a84648310a82fc4d330a5c0ee8ec43a0b01
Timestamp: 1705464581 Timestamp [UCT]: 2024-01-17 04:09:41 Age [y:d:h:m:s]: 01:145:03:47:29
Block: 937022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364899 RingCT/type: yes/0
Extra: 0113fde0ffeaa827cf32ea7bb1ae523a84648310a82fc4d330a5c0ee8ec43a0b0102110000000e59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06b854d6a4263196360bf10da14b3351743e35d395a34e055c37da1167b8dae0 0.600000000000 1395066 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": 937032, "vin": [ { "gen": { "height": 937022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06b854d6a4263196360bf10da14b3351743e35d395a34e055c37da1167b8dae0" } } ], "extra": [ 1, 19, 253, 224, 255, 234, 168, 39, 207, 50, 234, 123, 177, 174, 82, 58, 132, 100, 131, 16, 168, 47, 196, 211, 48, 165, 192, 238, 142, 196, 58, 11, 1, 2, 17, 0, 0, 0, 14, 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