Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a345a05004bfe75be2df377b71c9ab15e6a7c2040860051678d5821bffc237f7

Tx prefix hash: 9dabdb493d889a37a77bdd18b65d0f2cfa44c2269170cfa6c486dfb0a9e0e34c
Tx public key: bf9f1a77b9f82904da8ed40aa6c11938c7f6e0ea405155227186d654cab7f4b8
Timestamp: 1719638793 Timestamp [UCT]: 2024-06-29 05:26:33 Age [y:d:h:m:s]: 00:352:23:02:27
Block: 1054557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252149 RingCT/type: yes/0
Extra: 01bf9f1a77b9f82904da8ed40aa6c11938c7f6e0ea405155227186d654cab7f4b802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8484fc95dc4b11e1432a94bbbc47cd8b173ff78ab0504d1d6c4780b82aa293ab 0.600000000000 1524920 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": 1054567, "vin": [ { "gen": { "height": 1054557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8484fc95dc4b11e1432a94bbbc47cd8b173ff78ab0504d1d6c4780b82aa293ab" } } ], "extra": [ 1, 191, 159, 26, 119, 185, 248, 41, 4, 218, 142, 212, 10, 166, 193, 25, 56, 199, 246, 224, 234, 64, 81, 85, 34, 113, 134, 214, 84, 202, 183, 244, 184, 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