Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90c7512fa6e2400db8fecf56200d05ec9ddee2d6a45f9ee7a1a7179587f04a6f

Tx prefix hash: c192a29c6c5b3fbf7d7c012673a40c1db521ba0d646267374f51ee8df717baa5
Tx public key: 77d91958024211578f1c18cc87d15332815faf20ae79e9fc7fbf12cb562320e0
Timestamp: 1737403149 Timestamp [UCT]: 2025-01-20 19:59:09 Age [y:d:h:m:s]: 00:334:06:00:48
Block: 1201647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236484 RingCT/type: yes/0
Extra: 0177d91958024211578f1c18cc87d15332815faf20ae79e9fc7fbf12cb562320e0021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2665bcd3ae60af2c29b6d8a60f58015d666b28ef0e403a23b42f051096285c0b 0.600000000000 1688304 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": 1201657, "vin": [ { "gen": { "height": 1201647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2665bcd3ae60af2c29b6d8a60f58015d666b28ef0e403a23b42f051096285c0b" } } ], "extra": [ 1, 119, 217, 25, 88, 2, 66, 17, 87, 143, 28, 24, 204, 135, 209, 83, 50, 129, 95, 175, 32, 174, 121, 233, 252, 127, 191, 18, 203, 86, 35, 32, 224, 2, 17, 0, 0, 0, 4, 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