Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6304b0ba24cc26dbe646ff1df121f9cf6b57e498dcc900b606ed8c338e7ca32

Tx prefix hash: 124fa067bffc80d037d7cac0dd4ef741852942e0dab2bf01a178a83ed7fea2ce
Tx public key: 8b955713a3ae733572ae3bda1bccb30461386acb3b655f4981e5209ade65fb29
Timestamp: 1702124940 Timestamp [UCT]: 2023-12-09 12:29:00 Age [y:d:h:m:s]: 01:119:08:09:31
Block: 909357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346428 RingCT/type: yes/0
Extra: 018b955713a3ae733572ae3bda1bccb30461386acb3b655f4981e5209ade65fb290211000000014b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1dcd83434b8a7be7db363fe3a0d8dc733851344b7dc9b46ecd99431b5df73a70 0.600000000000 1366438 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": 909367, "vin": [ { "gen": { "height": 909357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dcd83434b8a7be7db363fe3a0d8dc733851344b7dc9b46ecd99431b5df73a70" } } ], "extra": [ 1, 139, 149, 87, 19, 163, 174, 115, 53, 114, 174, 59, 218, 27, 204, 179, 4, 97, 56, 106, 203, 59, 101, 95, 73, 129, 229, 32, 154, 222, 101, 251, 41, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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