Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d67fb8a1477860c32cc7555c3694a231cb897b5369726177b2d531304efbe1f

Tx prefix hash: 06ddd4d20e2781b54036eecb5d68650ec35298c563763a2ededd911b2c7d9962
Tx public key: 23360280a272955f6cde862225e56c95e8db8a7d12b8ad1d2a9590066b5f7212
Timestamp: 1723677386 Timestamp [UCT]: 2024-08-14 23:16:26 Age [y:d:h:m:s]: 00:288:16:01:01
Block: 1088039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206243 RingCT/type: yes/0
Extra: 0123360280a272955f6cde862225e56c95e8db8a7d12b8ad1d2a9590066b5f7212021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b9519c3fc0ef61388a9ba0e9dc3a5c38f1c3aaf7b95304173cf28735ea86172 0.600000000000 1562650 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": 1088049, "vin": [ { "gen": { "height": 1088039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b9519c3fc0ef61388a9ba0e9dc3a5c38f1c3aaf7b95304173cf28735ea86172" } } ], "extra": [ 1, 35, 54, 2, 128, 162, 114, 149, 95, 108, 222, 134, 34, 37, 229, 108, 149, 232, 219, 138, 125, 18, 184, 173, 29, 42, 149, 144, 6, 107, 95, 114, 18, 2, 17, 0, 0, 0, 4, 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