Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf962a03888fe0198f76ec1d4bc6552bf83604bce05bad2b9406d8928f384a55

Tx prefix hash: 881bb060ef4fb4f1f8d3128a9bc653087729341b4fb42ab9e0fe0965d0a2eaaf
Tx public key: 785d306e2d4b93432548f17795cf8a51cd9d2109767ef101d8323f21709ceae3
Timestamp: 1612744599 Timestamp [UTC]: 2021-02-08 00:36:39 Age [y:d:h:m:s]: 05:281:20:11:44
Block: 194178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1484976 RingCT/type: yes/0
Extra: 01785d306e2d4b93432548f17795cf8a51cd9d2109767ef101d8323f21709ceae302110000020127e2517e000000000000000000

1 output(s) for total of 0.139513374574 xmr

stealth address amount amount idx tag
00: 8a6a3513f85ed1e8cacf3aed4caea105a0263345aefdb7ca364fdfb56acd5671 0.139513374574 393828 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 dinastycoin-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": 194188, "vin": [ { "gen": { "height": 194178 } } ], "vout": [ { "amount": 139513374574, "target": { "key": "8a6a3513f85ed1e8cacf3aed4caea105a0263345aefdb7ca364fdfb56acd5671" } } ], "extra": [ 1, 120, 93, 48, 110, 45, 75, 147, 67, 37, 72, 241, 119, 149, 207, 138, 81, 205, 157, 33, 9, 118, 126, 241, 1, 216, 50, 63, 33, 112, 156, 234, 227, 2, 17, 0, 0, 2, 1, 39, 226, 81, 126, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: