Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 553e776019a42919b522ff0774380fd97cd2ca38a972f21efd64c78a2096b093

Tx prefix hash: 209f70b4db309c556e5b3766fba46840e109cdf391ad2aac3b3ce628430c6d6e
Tx public key: 4ee667789e9d6c0ec17234d1fccfb482b77e4bcdd0d3437ea7cf30495c8571f9
Timestamp: 1709915545 Timestamp [UCT]: 2024-03-08 16:32:25 Age [y:d:h:m:s]: 01:248:00:07:28
Block: 973959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435958 RingCT/type: yes/0
Extra: 014ee667789e9d6c0ec17234d1fccfb482b77e4bcdd0d3437ea7cf30495c8571f902110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e2ffbdf896c0446fda2ff6ac25b33393a2adb53e3e38a4af1cdf016c199c329 0.600000000000 1433902 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": 973969, "vin": [ { "gen": { "height": 973959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e2ffbdf896c0446fda2ff6ac25b33393a2adb53e3e38a4af1cdf016c199c329" } } ], "extra": [ 1, 78, 230, 103, 120, 158, 157, 108, 14, 193, 114, 52, 209, 252, 207, 180, 130, 183, 126, 75, 205, 208, 211, 67, 126, 167, 207, 48, 73, 92, 133, 113, 249, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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