Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95fc73ec610d54e11f8c8400d6cda4cbf5e82212e07abbc3a2eaa2793acf7e1c

Tx prefix hash: 74763122ad94cfcb4afa52813f02c6b6a0796c92968f6a369e7fdbc2ed23c024
Tx public key: 08bb72eb1696688b5d8adc6bc29bca402a46289075d48134311d14b4c82fb634
Timestamp: 1737024033 Timestamp [UCT]: 2025-01-16 10:40:33 Age [y:d:h:m:s]: 00:060:01:49:59
Block: 1198539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42730 RingCT/type: yes/0
Extra: 0108bb72eb1696688b5d8adc6bc29bca402a46289075d48134311d14b4c82fb634021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86914c7c990f396b19036d5c53eb3ea1f62d0fe43e9e567d9e2a15f50f0243a9 0.600000000000 1685164 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": 1198549, "vin": [ { "gen": { "height": 1198539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86914c7c990f396b19036d5c53eb3ea1f62d0fe43e9e567d9e2a15f50f0243a9" } } ], "extra": [ 1, 8, 187, 114, 235, 22, 150, 104, 139, 93, 138, 220, 107, 194, 155, 202, 64, 42, 70, 40, 144, 117, 212, 129, 52, 49, 29, 20, 180, 200, 47, 182, 52, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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