Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 046b0755ffce7f24e85edc9995a6a8a48bb14f82c5dd2447a222622281833566

Tx prefix hash: d5c7c134e8d7d6f94623a51bd30fdfae85974fa7043625207a4248effe39bf48
Tx public key: 7cec830a4f1935881c3ddc8133ce8e684cc6a49c9c5874c5e904b9b67c11b38c
Timestamp: 1721028091 Timestamp [UCT]: 2024-07-15 07:21:31 Age [y:d:h:m:s]: 00:257:05:23:48
Block: 1066091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183749 RingCT/type: yes/0
Extra: 017cec830a4f1935881c3ddc8133ce8e684cc6a49c9c5874c5e904b9b67c11b38c021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1515bd11ec48421040d0b63f901e44a637f9942efc9a3fc6bf0baa16fa986e35 0.600000000000 1536664 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": 1066101, "vin": [ { "gen": { "height": 1066091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1515bd11ec48421040d0b63f901e44a637f9942efc9a3fc6bf0baa16fa986e35" } } ], "extra": [ 1, 124, 236, 131, 10, 79, 25, 53, 136, 28, 61, 220, 129, 51, 206, 142, 104, 76, 198, 164, 156, 156, 88, 116, 197, 233, 4, 185, 182, 124, 17, 179, 140, 2, 17, 0, 0, 0, 7, 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