Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79820599cc6ed6378177e7f80f2d6abe6a4ad420b2b37d2c59067bca58c1f840

Tx prefix hash: 3e89cab47eb3a664b6d542feecb255e2f967bd7e09fec1bda1597686aa9e947f
Tx public key: 224fdeb86bae896d56f98ec8cef2bbfc75f1f26b0d04527d057235f28bc2d21a
Timestamp: 1721144566 Timestamp [UCT]: 2024-07-16 15:42:46 Age [y:d:h:m:s]: 00:255:16:41:40
Block: 1067056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182655 RingCT/type: yes/0
Extra: 01224fdeb86bae896d56f98ec8cef2bbfc75f1f26b0d04527d057235f28bc2d21a021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cb588ebd40a21cabcdb86b816d46dc72db096d1240cfa3880ef4fdc2e071757 0.600000000000 1537767 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": 1067066, "vin": [ { "gen": { "height": 1067056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cb588ebd40a21cabcdb86b816d46dc72db096d1240cfa3880ef4fdc2e071757" } } ], "extra": [ 1, 34, 79, 222, 184, 107, 174, 137, 109, 86, 249, 142, 200, 206, 242, 187, 252, 117, 241, 242, 107, 13, 4, 82, 125, 5, 114, 53, 242, 139, 194, 210, 26, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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