Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f1c5aa2ac1722cd6f55a7b2ddc58c21d6ebb113d8a6c4423b54d2cc99fa7871

Tx prefix hash: cf8e1605064af455bcc00c239c4ac10b01d30969a4529f1bc14a2f29d521b3e3
Tx public key: d6f1d4e89ea0f21fe0fa4898cd91a06f7683e89b2625f75ee9e4929f503472ae
Timestamp: 1787789825 Timestamp [UTC]: 2026-08-27 00:17:05 Age [y:d:h:m:s]: 00:081:07:46:58
Block: 1621778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 57733 RingCT/type: yes/0
Extra: 01d6f1d4e89ea0f21fe0fa4898cd91a06f7683e89b2625f75ee9e4929f503472ae

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d50e4ec117b53040f91a5989f3d2d4acca58ff1874310d415a5a04733055c0c0 0.000600000000 2111798 of 15 <b4>

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": 1621788, "vin": [ { "gen": { "height": 1621778 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "d50e4ec117b53040f91a5989f3d2d4acca58ff1874310d415a5a04733055c0c0", "view_tag": "b4" } } } ], "extra": [ 1, 214, 241, 212, 232, 158, 160, 242, 31, 224, 250, 72, 152, 205, 145, 160, 111, 118, 131, 232, 155, 38, 37, 247, 94, 233, 228, 146, 159, 80, 52, 114, 174 ], "rct_signatures": { "type": 0 } }


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