Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc60e8fe5c28c12e0bf515bb579f69456dd5f47e245422d7c7c33fba3c593beb

Tx prefix hash: 0ca7687717b9d0791fcfdb8cf6518526428527ee5ef5eef35d6d7c3b6b9e737f
Tx public key: c2ff193366db24e3d2ea9ed0334dae632bb121585fc31b9cb93f42a8532ea248
Timestamp: 1710848552 Timestamp [UCT]: 2024-03-19 11:42:32 Age [y:d:h:m:s]: 00:340:00:13:58
Block: 981710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243052 RingCT/type: yes/0
Extra: 01c2ff193366db24e3d2ea9ed0334dae632bb121585fc31b9cb93f42a8532ea24802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6207c1f31e4040cc84a086b96a20fa900bfa20bc3d906e03741fcd2cdc8992cb 0.600000000000 1441807 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": 981720, "vin": [ { "gen": { "height": 981710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6207c1f31e4040cc84a086b96a20fa900bfa20bc3d906e03741fcd2cdc8992cb" } } ], "extra": [ 1, 194, 255, 25, 51, 102, 219, 36, 227, 210, 234, 158, 208, 51, 77, 174, 99, 43, 177, 33, 88, 95, 195, 27, 156, 185, 63, 66, 168, 83, 46, 162, 72, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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