Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b78d5d4efb049450e91c6ddc8c0317952277c05a7d941d69144be000824351f4

Tx prefix hash: 5389679bc8547feafb3c921917dbae27d38268b0effadb4832c094c1322a2316
Tx public key: 7dce5bbcfe0b6a4d781146498c416d0ed1713c643844d8d2f313fe269fc4974e
Timestamp: 1726483860 Timestamp [UCT]: 2024-09-16 10:51:00 Age [y:d:h:m:s]: 00:116:02:20:11
Block: 1111312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83018 RingCT/type: yes/0
Extra: 017dce5bbcfe0b6a4d781146498c416d0ed1713c643844d8d2f313fe269fc4974e021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36fa7ab96f2c0474390a11aac8ac05701193841e532bd455b796b1d85dbd28e8 0.600000000000 1590227 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": 1111322, "vin": [ { "gen": { "height": 1111312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36fa7ab96f2c0474390a11aac8ac05701193841e532bd455b796b1d85dbd28e8" } } ], "extra": [ 1, 125, 206, 91, 188, 254, 11, 106, 77, 120, 17, 70, 73, 140, 65, 109, 14, 209, 113, 60, 100, 56, 68, 216, 210, 243, 19, 254, 38, 159, 196, 151, 78, 2, 17, 0, 0, 0, 8, 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