Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5d1c8b214a8a81dbb36dd93de6638867199e19a3424a722998fdcff0567c5f0

Tx prefix hash: 6a874b680b8e37e9d7f6c49a6f333aa254f706d9a4784f4416f306d9c0c4e586
Tx public key: 0374b36cbc0345843c3b8604974eb038e823d5543f3a5fb262fd5d45e2ed7547
Timestamp: 1745248134 Timestamp [UCT]: 2025-04-21 15:08:54 Age [y:d:h:m:s]: 00:020:02:03:30
Block: 1266357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14372 RingCT/type: yes/0
Extra: 010374b36cbc0345843c3b8604974eb038e823d5543f3a5fb262fd5d45e2ed75470211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6bce459bc43e5c9cea2aa1adb2f400a2c04062991d8eedda43e602546de8eba 0.600000000000 1753578 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": 1266367, "vin": [ { "gen": { "height": 1266357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6bce459bc43e5c9cea2aa1adb2f400a2c04062991d8eedda43e602546de8eba" } } ], "extra": [ 1, 3, 116, 179, 108, 188, 3, 69, 132, 60, 59, 134, 4, 151, 78, 176, 56, 232, 35, 213, 84, 63, 58, 95, 178, 98, 253, 93, 69, 226, 237, 117, 71, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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