Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5922ef854f7d10d067b3689707e45eb2b8baff3cb7008deebdb851aab5c3a9ab

Tx prefix hash: 5c38f0032d43612c462ce4f5e4f318eb109c827993a453233ba97836035154fe
Tx public key: 8f854ff6fe76c0861f65a4933d80d5a99568c1a7345d974576102f5f05f8d87d
Timestamp: 1699687531 Timestamp [UCT]: 2023-11-11 07:25:31 Age [y:d:h:m:s]: 01:105:11:55:00
Block: 889160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336541 RingCT/type: yes/0
Extra: 018f854ff6fe76c0861f65a4933d80d5a99568c1a7345d974576102f5f05f8d87d021100000004faf35c9c000000000000000000

1 output(s) for total of 0.694774406000 dcy

stealth address amount amount idx
00: 0bb7f2b575dbf3d35337ae072cc01de94081f17b98650160c916b22119e1f677 0.694774406000 1345137 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": 889170, "vin": [ { "gen": { "height": 889160 } } ], "vout": [ { "amount": 694774406, "target": { "key": "0bb7f2b575dbf3d35337ae072cc01de94081f17b98650160c916b22119e1f677" } } ], "extra": [ 1, 143, 133, 79, 246, 254, 118, 192, 134, 31, 101, 164, 147, 61, 128, 213, 169, 149, 104, 193, 167, 52, 93, 151, 69, 118, 16, 47, 95, 5, 248, 216, 125, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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