Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a19deab21e4d81cbf1c374b297070af8f5ba67aa3de510596dfe9510e13df18

Tx prefix hash: bfd3f7dc7e32737226365c3b07118c0e275657d56579d595700171d36f6620c9
Tx public key: f4798008a556115cc28f7508dfdf26d4c82dfc6bec82026fde0d73eebc9c45e2
Timestamp: 1711674332 Timestamp [UTC]: 2024-03-29 01:05:32 Age [y:d:h:m:s]: 02:237:15:33:39
Block: 988553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 694941 RingCT/type: yes/0
Extra: 01f4798008a556115cc28f7508dfdf26d4c82dfc6bec82026fde0d73eebc9c45e20211000000010011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8c885b4ef622af4433eb1eacf32011c341a25eb1dfed40ad74eae1459471ee3e 0.000600000000 1448832 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 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": 988563, "vin": [ { "gen": { "height": 988553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c885b4ef622af4433eb1eacf32011c341a25eb1dfed40ad74eae1459471ee3e" } } ], "extra": [ 1, 244, 121, 128, 8, 165, 86, 17, 92, 194, 143, 117, 8, 223, 223, 38, 212, 200, 45, 252, 107, 236, 130, 2, 111, 222, 13, 115, 238, 188, 156, 69, 226, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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: