Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccbec006c4f9e6bdffeb1a509ad4ef650400791aa7572dbdc80a0904b2c0c027

Tx prefix hash: ddeb7555b7e8ec3deb3c60b2adc5bac0f74651724d8eb04ea27448d7b08da6f1
Tx public key: 92a4909eb428a163cefa935ef4827977291bcf5905e97d1f6fb0b8cb1fed7305
Timestamp: 1736424826 Timestamp [UCT]: 2025-01-09 12:13:46 Age [y:d:h:m:s]: 00:305:12:19:43
Block: 1193589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215856 RingCT/type: yes/0
Extra: 0192a4909eb428a163cefa935ef4827977291bcf5905e97d1f6fb0b8cb1fed73050211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e36770455f09ea2c4d8a00446f78ff63d5ecc3c2d87b7e042cc6d677390a67b 0.600000000000 1680152 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": 1193599, "vin": [ { "gen": { "height": 1193589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e36770455f09ea2c4d8a00446f78ff63d5ecc3c2d87b7e042cc6d677390a67b" } } ], "extra": [ 1, 146, 164, 144, 158, 180, 40, 161, 99, 206, 250, 147, 94, 244, 130, 121, 119, 41, 27, 207, 89, 5, 233, 125, 31, 111, 176, 184, 203, 31, 237, 115, 5, 2, 17, 0, 0, 0, 3, 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