Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c7c7c5850ee71344be4f7fdaf33e1753835c6d1c7439e9f740799ca2c40e21e

Tx prefix hash: bdd20c9c78f6e00fca4dddf772486d629f039b066397a8481af17eb39a2413d7
Tx public key: 898bb9b0d7a692f6953381c0858e6ffccedbdf8629d1cdc7405193955ed674c6
Timestamp: 1751571729 Timestamp [UCT]: 2025-07-03 19:42:09 Age [y:d:h:m:s]: 00:133:04:27:32
Block: 1318135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93448 RingCT/type: yes/0
Extra: 01898bb9b0d7a692f6953381c0858e6ffccedbdf8629d1cdc7405193955ed674c6021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d644e3273f38ea2bbc6734b6ae8420e45ff818de8d8ee4be2ecd7f4cb34b224 0.600000000000 1805808 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": 1318145, "vin": [ { "gen": { "height": 1318135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d644e3273f38ea2bbc6734b6ae8420e45ff818de8d8ee4be2ecd7f4cb34b224" } } ], "extra": [ 1, 137, 139, 185, 176, 215, 166, 146, 246, 149, 51, 129, 192, 133, 142, 111, 252, 206, 219, 223, 134, 41, 209, 205, 199, 64, 81, 147, 149, 94, 214, 116, 198, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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