Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba051ab7223776e94d57c6589e7dc95a7c4f25ea537169ae52878ff5e0971731

Tx prefix hash: 842c27d7dfcedc45ceb26f2c562af9fc6daf3c00021428839569eafb7ef30e3d
Tx public key: f55bf36b33135122f3a1d6a6b0810998465be3df4df190dc062045f126a35f32
Timestamp: 1749496949 Timestamp [UCT]: 2025-06-09 19:22:29 Age [y:d:h:m:s]: 00:158:23:36:30
Block: 1301557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111297 RingCT/type: yes/0
Extra: 01f55bf36b33135122f3a1d6a6b0810998465be3df4df190dc062045f126a35f32021100000008bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf715529c6e9219ebf37620244880d0f636cdb447c8df821a5125ed66e41f33a 0.600000000000 1789116 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": 1301567, "vin": [ { "gen": { "height": 1301557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf715529c6e9219ebf37620244880d0f636cdb447c8df821a5125ed66e41f33a" } } ], "extra": [ 1, 245, 91, 243, 107, 51, 19, 81, 34, 243, 161, 214, 166, 176, 129, 9, 152, 70, 91, 227, 223, 77, 241, 144, 220, 6, 32, 69, 241, 38, 163, 95, 50, 2, 17, 0, 0, 0, 8, 191, 81, 178, 162, 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