Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3f5928974c955e462007ecc4fb934abbe0abeffc29d2cce411b0e411542f959

Tx prefix hash: 30dd04f646dd5134b324e1fbd95494d1a184234efcbb5ba46aa44fdacb612fbf
Tx public key: 6516918be6d6f0b8b583d4a1eff7ee9a6eb7f1fe4f3c867f8638c79f19bc68b0
Timestamp: 1699499191 Timestamp [UCT]: 2023-11-09 03:06:31 Age [y:d:h:m:s]: 01:133:00:20:03
Block: 887596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356266 RingCT/type: yes/0
Extra: 016516918be6d6f0b8b583d4a1eff7ee9a6eb7f1fe4f3c867f8638c79f19bc68b00211000000044b8f5122000000000000000000

1 output(s) for total of 0.703114404000 dcy

stealth address amount amount idx
00: f62f52f3fcf3d3e65fc9f0ca94e9efb703a7a7d609b09c278c1b2137f087547f 0.703114404000 1343483 of 0

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": 887606, "vin": [ { "gen": { "height": 887596 } } ], "vout": [ { "amount": 703114404, "target": { "key": "f62f52f3fcf3d3e65fc9f0ca94e9efb703a7a7d609b09c278c1b2137f087547f" } } ], "extra": [ 1, 101, 22, 145, 139, 230, 214, 240, 184, 181, 131, 212, 161, 239, 247, 238, 154, 110, 183, 241, 254, 79, 60, 134, 127, 134, 56, 199, 159, 25, 188, 104, 176, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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