Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d822b3100b7d15bcb358ec38e74c303360172b3a6ea21d91c690ea47a7e9f637

Tx prefix hash: 36a686c461b23e2a29dda1e272b501f42c32a4daa5f41de6c880d3e8eefb5aad
Tx public key: 63cc3a372155754c313e0e5917d3830c1bdde2bf2fcee96616ce28ab8da31e43
Timestamp: 1730155487 Timestamp [UCT]: 2024-10-28 22:44:47 Age [y:d:h:m:s]: 00:073:06:04:31
Block: 1141682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52397 RingCT/type: yes/0
Extra: 0163cc3a372155754c313e0e5917d3830c1bdde2bf2fcee96616ce28ab8da31e430211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55d12103dbc60576fa9e751904e387ceef3a259e686b3f6d456b37e0cb9b4d0b 0.600000000000 1625493 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": 1141692, "vin": [ { "gen": { "height": 1141682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55d12103dbc60576fa9e751904e387ceef3a259e686b3f6d456b37e0cb9b4d0b" } } ], "extra": [ 1, 99, 204, 58, 55, 33, 85, 117, 76, 49, 62, 14, 89, 23, 211, 131, 12, 27, 221, 226, 191, 47, 206, 233, 102, 22, 206, 40, 171, 141, 163, 30, 67, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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