Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f84bde5a5fe1e4790c62f567fc0c9bd206ac0be586461f062b905f7ae05e43e3

Tx prefix hash: 4a37815636bc1e68227f3adfc5d8299b1a0c96f0095d2775297cf4b1af9c7574
Tx public key: c6552fa757fa5ef5b2214797d75a21ef50de1e7adc299124611e044354b37d4a
Timestamp: 1694722137 Timestamp [UCT]: 2023-09-14 20:08:57 Age [y:d:h:m:s]: 01:131:18:21:00
Block: 848178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355448 RingCT/type: yes/0
Extra: 01c6552fa757fa5ef5b2214797d75a21ef50de1e7adc299124611e044354b37d4a02110000000433af99f4000000000000000000

1 output(s) for total of 0.949804559000 dcy

stealth address amount amount idx
00: e34b706b78784e64a8c8cd1e41945ce886bf45d91153abd2d1df99c7a4562b55 0.949804559000 1301764 of 0

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": 848188, "vin": [ { "gen": { "height": 848178 } } ], "vout": [ { "amount": 949804559, "target": { "key": "e34b706b78784e64a8c8cd1e41945ce886bf45d91153abd2d1df99c7a4562b55" } } ], "extra": [ 1, 198, 85, 47, 167, 87, 250, 94, 245, 178, 33, 71, 151, 215, 90, 33, 239, 80, 222, 30, 122, 220, 41, 145, 36, 97, 30, 4, 67, 84, 179, 125, 74, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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