Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e06b8c5c709f80fff05d025f1275d7045bcdd3064d97a765463e051c6f0dffe

Tx prefix hash: 79a1b95477273d9ab12687d63a1ddddea3a32b8a7b2f3db211b2b72fee442c2f
Tx public key: db378c81d3460117c75effb2c066a72321d54ff0e0fe4bce84a08619980d6265
Timestamp: 1705554634 Timestamp [UCT]: 2024-01-18 05:10:34 Age [y:d:h:m:s]: 01:042:16:31:39
Block: 937767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291589 RingCT/type: yes/0
Extra: 01db378c81d3460117c75effb2c066a72321d54ff0e0fe4bce84a08619980d626502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d30550c4ef3fa6d3e0d691ff5889b71ede26f475601f9049a063075faf1a9c4c 0.600000000000 1395831 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": 937777, "vin": [ { "gen": { "height": 937767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d30550c4ef3fa6d3e0d691ff5889b71ede26f475601f9049a063075faf1a9c4c" } } ], "extra": [ 1, 219, 55, 140, 129, 211, 70, 1, 23, 199, 94, 255, 178, 192, 102, 167, 35, 33, 213, 79, 240, 224, 254, 75, 206, 132, 160, 134, 25, 152, 13, 98, 101, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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