Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ab09c56598d167d39ae068e8a214f1d3feb7bb364d924c68fab26607ce9254d

Tx prefix hash: f8dd3229649830f1820554e71e78ee2028087e9e4b53d19e584b7bbeb54bd8a8
Tx public key: bdd6cadd9e1889a137ed13938ea8d7e3b1e5b106bdae74abe584b69ff7038a85
Timestamp: 1732658153 Timestamp [UCT]: 2024-11-26 21:55:53 Age [y:d:h:m:s]: 00:129:14:54:48
Block: 1162394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92455 RingCT/type: yes/0
Extra: 01bdd6cadd9e1889a137ed13938ea8d7e3b1e5b106bdae74abe584b69ff7038a850211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7deb357119acb71208a09494f5f97b2de379a0721dcb27f833dd41e0c78f26f2 0.600000000000 1648049 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": 1162404, "vin": [ { "gen": { "height": 1162394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7deb357119acb71208a09494f5f97b2de379a0721dcb27f833dd41e0c78f26f2" } } ], "extra": [ 1, 189, 214, 202, 221, 158, 24, 137, 161, 55, 237, 19, 147, 142, 168, 215, 227, 177, 229, 177, 6, 189, 174, 116, 171, 229, 132, 182, 159, 247, 3, 138, 133, 2, 17, 0, 0, 0, 4, 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