Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a9d1a03faf88a0e64a73d2a4b56db4f69eb495f82427ea7e0d53f5d14454daa

Tx prefix hash: d53d07a2adb8930c81fe2458e817d771e1370634536611f1c8680660766e8a16
Tx public key: 5fe61be65a7a1e0931052f2f9d73fd2ea8dce60d9e064946d069d626a8b670b3
Timestamp: 1729120922 Timestamp [UCT]: 2024-10-16 23:22:02 Age [y:d:h:m:s]: 00:148:19:46:04
Block: 1133176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106146 RingCT/type: yes/0
Extra: 015fe61be65a7a1e0931052f2f9d73fd2ea8dce60d9e064946d069d626a8b670b302110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 641f761e816856bf1de965dcc4a51c338899cedfdd47416071c311fa8f6d5df2 0.600000000000 1616247 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": 1133186, "vin": [ { "gen": { "height": 1133176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "641f761e816856bf1de965dcc4a51c338899cedfdd47416071c311fa8f6d5df2" } } ], "extra": [ 1, 95, 230, 27, 230, 90, 122, 30, 9, 49, 5, 47, 47, 157, 115, 253, 46, 168, 220, 230, 13, 158, 6, 73, 70, 208, 105, 214, 38, 168, 182, 112, 179, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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