Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d70b85bcf28bf6cdde1a7047b01569a912750d4cab752c72d95d5b19f0dab69d

Tx prefix hash: 777a27330f278cb2eda933abb922d814768b321eb3f527c0d2ed3071af01c837
Tx public key: a63e5b78b5c448a9ce994ceff86f7f7735ee990f59689462370f2f7817ec9178
Timestamp: 1772236110 Timestamp [UTC]: 2026-02-27 23:48:30 Age [y:d:h:m:s]: 00:265:18:30:02
Block: 1487249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195610 RingCT/type: yes/0
Extra: 01a63e5b78b5c448a9ce994ceff86f7f7735ee990f59689462370f2f7817ec9178021100000008e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 508747e40ec91b3b93ce6318e681b329556ea8a6afdeb1b70deb56dc8f021da7 0.000600000000 1976717 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": 1487259, "vin": [ { "gen": { "height": 1487249 } } ], "vout": [ { "amount": 600000000, "target": { "key": "508747e40ec91b3b93ce6318e681b329556ea8a6afdeb1b70deb56dc8f021da7" } } ], "extra": [ 1, 166, 62, 91, 120, 181, 196, 72, 169, 206, 153, 76, 239, 248, 111, 127, 119, 53, 238, 153, 15, 89, 104, 148, 98, 55, 15, 47, 120, 23, 236, 145, 120, 2, 17, 0, 0, 0, 8, 228, 245, 25, 63, 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: