Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 117387aae556cf835e584249054de7d69714d5089ff2d4a5c4df13d5c52519f4

Tx prefix hash: 617e3156a43857fa158762b62b92f5aaac0ff4c92767da1d97819f2ff8f5e4b5
Tx public key: c3fe9c4350c1e5c6be9684f6cb0f87dfee723ed09a5d0ff64fd886114f21f81b
Timestamp: 1720575312 Timestamp [UCT]: 2024-07-10 01:35:12 Age [y:d:h:m:s]: 00:248:13:20:11
Block: 1062333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177583 RingCT/type: yes/0
Extra: 01c3fe9c4350c1e5c6be9684f6cb0f87dfee723ed09a5d0ff64fd886114f21f81b021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eab63093dabdf0901dd2e57cf4d9a6c35a4e51283c85ddf169fd0b45d3e32773 0.600000000000 1532834 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": 1062343, "vin": [ { "gen": { "height": 1062333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eab63093dabdf0901dd2e57cf4d9a6c35a4e51283c85ddf169fd0b45d3e32773" } } ], "extra": [ 1, 195, 254, 156, 67, 80, 193, 229, 198, 190, 150, 132, 246, 203, 15, 135, 223, 238, 114, 62, 208, 154, 93, 15, 246, 79, 216, 134, 17, 79, 33, 248, 27, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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