Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 290b4d8bf31cd04bbce49d0baaef0054b9f28a014720fa3a280d3778b1d109ce

Tx prefix hash: 2bcb8f6dbcb7a0e9ecb4cf6e5afa2813c7b8c866706bbf8d8d2a7aea789b7932
Tx public key: 66a9b9b3244af855db64cd6e9f31ff10154ada846204f89d112e4fb57b85658f
Timestamp: 1742714843 Timestamp [UCT]: 2025-03-23 07:27:23 Age [y:d:h:m:s]: 00:243:16:32:16
Block: 1245400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171894 RingCT/type: yes/0
Extra: 0166a9b9b3244af855db64cd6e9f31ff10154ada846204f89d112e4fb57b85658f021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c92fb3b193a29cd0af36d6a49cf514188116d4d04e878098c01f5617db019f1b 0.600000000000 1732391 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": 1245410, "vin": [ { "gen": { "height": 1245400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c92fb3b193a29cd0af36d6a49cf514188116d4d04e878098c01f5617db019f1b" } } ], "extra": [ 1, 102, 169, 185, 179, 36, 74, 248, 85, 219, 100, 205, 110, 159, 49, 255, 16, 21, 74, 218, 132, 98, 4, 248, 157, 17, 46, 79, 181, 123, 133, 101, 143, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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