Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f61d4516175e89ef56ccbd1757af7de3a7c67d8d86da0da9fbfcfd98101bda83

Tx prefix hash: 960c32a5d817c76c942983f5aeaadf7447225ec79f2a59f326f17d3746989fd1
Tx public key: 9cbab4c36407fa11d17a7f96ea27cfa5431f640ca28ae491bd341a20a8fe2bae
Timestamp: 1718556676 Timestamp [UCT]: 2024-06-16 16:51:16 Age [y:d:h:m:s]: 00:221:20:28:12
Block: 1045610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158700 RingCT/type: yes/0
Extra: 019cbab4c36407fa11d17a7f96ea27cfa5431f640ca28ae491bd341a20a8fe2bae0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e27a16587e179ab65e985ca1adce0fb8df449e9701cc5ae53873d8a37dd87697 0.600000000000 1515225 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": 1045620, "vin": [ { "gen": { "height": 1045610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e27a16587e179ab65e985ca1adce0fb8df449e9701cc5ae53873d8a37dd87697" } } ], "extra": [ 1, 156, 186, 180, 195, 100, 7, 250, 17, 209, 122, 127, 150, 234, 39, 207, 165, 67, 31, 100, 12, 162, 138, 228, 145, 189, 52, 26, 32, 168, 254, 43, 174, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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