Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f301d113fd4de4eaa6b5d13f6b9716f25de6af76b69444bec00ce0470e49a9ee

Tx prefix hash: 55d424ab1240d16018a29b0be01794c23512a35a5cfdcf1109b987485d3cd014
Tx public key: 8ba344f9aa30ea5fa5307250769549ee0a580bc49d801c0a4d458ba7cb23f233
Timestamp: 1771429206 Timestamp [UTC]: 2026-02-18 15:40:06 Age [y:d:h:m:s]: 00:272:08:48:34
Block: 1480576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200177 RingCT/type: yes/0
Extra: 018ba344f9aa30ea5fa5307250769549ee0a580bc49d801c0a4d458ba7cb23f233021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bf30510d3ef90486d7065158df1e7646e0da6c591fe03e2523acb035e574e686 0.000600000000 1969946 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": 1480586, "vin": [ { "gen": { "height": 1480576 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf30510d3ef90486d7065158df1e7646e0da6c591fe03e2523acb035e574e686" } } ], "extra": [ 1, 139, 163, 68, 249, 170, 48, 234, 95, 165, 48, 114, 80, 118, 149, 73, 238, 10, 88, 11, 196, 157, 128, 28, 10, 77, 69, 139, 167, 203, 35, 242, 51, 2, 17, 0, 0, 0, 4, 241, 136, 200, 168, 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: