Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ff3a9c77bf4cb1bf0b6b76b7557c3234f2ee8835a8a301b3b677a2b06f88240

Tx prefix hash: e0350e623ed5eb8264d3ac3fef5f3057e97a909fb1257710f5ca7e92f6f524fa
Tx public key: 5c55ba7cabb838ce361ebbeb4f6d5f053fe81e061875864fb6422105b89a56a0
Timestamp: 1715181471 Timestamp [UCT]: 2024-05-08 15:17:51 Age [y:d:h:m:s]: 00:340:14:29:01
Block: 1017624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243469 RingCT/type: yes/0
Extra: 015c55ba7cabb838ce361ebbeb4f6d5f053fe81e061875864fb6422105b89a56a002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 257fee4433357b5e1b891d735857a4e31612f0e1c9fa7ed50c79cce298ce9c9d 0.600000000000 1481407 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": 1017634, "vin": [ { "gen": { "height": 1017624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "257fee4433357b5e1b891d735857a4e31612f0e1c9fa7ed50c79cce298ce9c9d" } } ], "extra": [ 1, 92, 85, 186, 124, 171, 184, 56, 206, 54, 30, 187, 235, 79, 109, 95, 5, 63, 232, 30, 6, 24, 117, 134, 79, 182, 66, 33, 5, 184, 154, 86, 160, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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