Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01d1b808ba5718e3c6c7b0d078d5250faaa7f7f7a32fe6224083acf82e7c06ee

Tx prefix hash: dc004df7166dea8e5501799e17c3a4cdb02eef79dcef24868aa3696115a98106
Tx public key: fe7a8cc63ac1a2ea3c914d7fac04f2e33359df15d5238d5bb456137ec2eabca6
Timestamp: 1751848604 Timestamp [UTC]: 2025-07-07 00:36:44 Age [y:d:h:m:s]: 00:310:13:20:20
Block: 1320264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212614 RingCT/type: yes/0
Extra: 01fe7a8cc63ac1a2ea3c914d7fac04f2e33359df15d5238d5bb456137ec2eabca602110000000101491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 687b5f7ab19272d3ea904b5c5898ee77e4b7968bf3372811bf8f0085d829d6ca 0.000600000000 1807961 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": 1320274, "vin": [ { "gen": { "height": 1320264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "687b5f7ab19272d3ea904b5c5898ee77e4b7968bf3372811bf8f0085d829d6ca" } } ], "extra": [ 1, 254, 122, 140, 198, 58, 193, 162, 234, 60, 145, 77, 127, 172, 4, 242, 227, 51, 89, 223, 21, 213, 35, 141, 91, 180, 86, 19, 126, 194, 234, 188, 166, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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: