Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 030b91d11b7e3ac61ef7b5601625ff094051e1ec015808526991ba90cb997f0f

Tx prefix hash: 51732378d0aa101ec796cb71c195cb92d4e075377cd7f727b824acd3c1237656
Tx public key: a81f57327a3d830ef3bc63f2abec203b80e8f5c4f1a410ba006416065d1d5c0c
Timestamp: 1736346040 Timestamp [UCT]: 2025-01-08 14:20:40 Age [y:d:h:m:s]: 00:107:19:37:58
Block: 1192930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76859 RingCT/type: yes/0
Extra: 01a81f57327a3d830ef3bc63f2abec203b80e8f5c4f1a410ba006416065d1d5c0c0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81f932e16bc3428fe01117b57f83f347cfc9214bcfceb08e394cc1a236b23e5d 0.600000000000 1679487 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": 1192940, "vin": [ { "gen": { "height": 1192930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81f932e16bc3428fe01117b57f83f347cfc9214bcfceb08e394cc1a236b23e5d" } } ], "extra": [ 1, 168, 31, 87, 50, 122, 61, 131, 14, 243, 188, 99, 242, 171, 236, 32, 59, 128, 232, 245, 196, 241, 164, 16, 186, 0, 100, 22, 6, 93, 29, 92, 12, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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