Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 571787d8e4ba8f930a51cda4bb25a338b9b68ac63d03dea48103d9eb31086927

Tx prefix hash: 6cc36d2db8c9857c623165c345b3ed381932b3b2a2ff7f1134c37b80219e0ba3
Tx public key: e9edae5973af5a71e0c4b1a4ff541e293fecabe18db6e8be4ae388115c0a9df8
Timestamp: 1750171954 Timestamp [UTC]: 2025-06-17 14:52:34 Age [y:d:h:m:s]: 01:067:04:54:06
Block: 1307014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312418 RingCT/type: yes/0
Extra: 01e9edae5973af5a71e0c4b1a4ff541e293fecabe18db6e8be4ae388115c0a9df802110000000443846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e4bc7fa5b0942af6795cdfea0222c09a4c4a15b0ea1cba7e5fa8bb7715efbea7 0.000600000000 1794623 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": 1307024, "vin": [ { "gen": { "height": 1307014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4bc7fa5b0942af6795cdfea0222c09a4c4a15b0ea1cba7e5fa8bb7715efbea7" } } ], "extra": [ 1, 233, 237, 174, 89, 115, 175, 90, 113, 224, 196, 177, 164, 255, 84, 30, 41, 63, 236, 171, 225, 141, 182, 232, 190, 74, 227, 136, 17, 92, 10, 157, 248, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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: