Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7575153d6d806904a70b98543d0c1b10096370aa044274750d2d82a9c44c69f

Tx prefix hash: 38b52241e3ed00f883fdad4654124a9dcce6751e5195748c5a32ab4a03c48a22
Tx public key: 41b8c6ec6a7817dc34f5eb23033e2cf90fae621985e2b206d039dbb26b546326
Timestamp: 1725775562 Timestamp [UCT]: 2024-09-08 06:06:02 Age [y:d:h:m:s]: 00:270:10:46:01
Block: 1105440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193198 RingCT/type: yes/0
Extra: 0141b8c6ec6a7817dc34f5eb23033e2cf90fae621985e2b206d039dbb26b54632602110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fb3daa813ed5dc229c6ecc75caec93f55117f9323b5dffee2cc7a2d4a6f8a62 0.600000000000 1582783 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": 1105450, "vin": [ { "gen": { "height": 1105440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fb3daa813ed5dc229c6ecc75caec93f55117f9323b5dffee2cc7a2d4a6f8a62" } } ], "extra": [ 1, 65, 184, 198, 236, 106, 120, 23, 220, 52, 245, 235, 35, 3, 62, 44, 249, 15, 174, 98, 25, 133, 226, 178, 6, 208, 57, 219, 178, 107, 84, 99, 38, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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