Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1d70e9029946f16441ea4dc1e684046a023694601fc0fe6e74f794bdf9fe5c0

Tx prefix hash: 09cca06419eea4f4a9128079e235abc9da222046e0841452dbaa7fe07518d185
Tx public key: fba5c7314e0e3edce7778dd0e293c28bb36af17dcdc96e50d0700197fd24b5fd
Timestamp: 1725715862 Timestamp [UCT]: 2024-09-07 13:31:02 Age [y:d:h:m:s]: 00:206:12:00:52
Block: 1104949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147404 RingCT/type: yes/0
Extra: 01fba5c7314e0e3edce7778dd0e293c28bb36af17dcdc96e50d0700197fd24b5fd021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f7834950ad2c63d2080f6f12bfe121dcc837f2d50c50921c86a1ced97c05f91 0.600000000000 1582284 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": 1104959, "vin": [ { "gen": { "height": 1104949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f7834950ad2c63d2080f6f12bfe121dcc837f2d50c50921c86a1ced97c05f91" } } ], "extra": [ 1, 251, 165, 199, 49, 78, 14, 62, 220, 231, 119, 141, 208, 226, 147, 194, 139, 179, 106, 241, 125, 205, 201, 110, 80, 208, 112, 1, 151, 253, 36, 181, 253, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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