Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ee0208b360a18791a37f7a653bd759cee273bfac6694b272462afeb62ffed86

Tx prefix hash: 529384d1d5d11019c6e41a465ba4e27c49856ed71a9c510c227e2dc791bf60ea
Tx public key: de0ec6d577e749aa00d72e16f2e8b06a1f066cce1fa04cd4cce5796abf3b7980
Timestamp: 1733729923 Timestamp [UCT]: 2024-12-09 07:38:43 Age [y:d:h:m:s]: 00:173:09:22:59
Block: 1171287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123759 RingCT/type: yes/0
Extra: 01de0ec6d577e749aa00d72e16f2e8b06a1f066cce1fa04cd4cce5796abf3b79800211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cae19a065cb0d8392a8700fb72c8b59f850acff326062f97fa8e566f087b7eaa 0.600000000000 1657026 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": 1171297, "vin": [ { "gen": { "height": 1171287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cae19a065cb0d8392a8700fb72c8b59f850acff326062f97fa8e566f087b7eaa" } } ], "extra": [ 1, 222, 14, 198, 213, 119, 231, 73, 170, 0, 215, 46, 22, 242, 232, 176, 106, 31, 6, 108, 206, 31, 160, 76, 212, 204, 229, 121, 106, 191, 59, 121, 128, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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