Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d13f2f2dfbb029adf5d5294aba833a671e2d77ee508601ed50d6d3e41534a379

Tx prefix hash: f34c99c42f68c93e17d6102bf65d5cf6a5ebc2779af3c01a07894c46351713d8
Tx public key: c6ec8cb94f4324a788d3f8fe1cc77ed65fca74390f214152ed230e875e52c496
Timestamp: 1700801187 Timestamp [UCT]: 2023-11-24 04:46:27 Age [y:d:h:m:s]: 01:135:06:32:25
Block: 898383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357846 RingCT/type: yes/0
Extra: 01c6ec8cb94f4324a788d3f8fe1cc77ed65fca74390f214152ed230e875e52c49602110000000133af99f4000000000000000000

1 output(s) for total of 0.647566197000 dcy

stealth address amount amount idx
00: 9e3f9ad7d24e06ff7db558cd0c2eaa88bf39666124387eb11c36cbe7dde496a4 0.647566197000 1354796 of 0

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": 898393, "vin": [ { "gen": { "height": 898383 } } ], "vout": [ { "amount": 647566197, "target": { "key": "9e3f9ad7d24e06ff7db558cd0c2eaa88bf39666124387eb11c36cbe7dde496a4" } } ], "extra": [ 1, 198, 236, 140, 185, 79, 67, 36, 167, 136, 211, 248, 254, 28, 199, 126, 214, 95, 202, 116, 57, 15, 33, 65, 82, 237, 35, 14, 135, 94, 82, 196, 150, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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