Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1088e2925de6b5077b2ded39b8b7259dd1e304cd8ed7bf464e46a69708945d9

Tx prefix hash: 78012a6a231c233c69dbee5d9fba2388a773ae101597ada8ecaf3b8efe112ced
Tx public key: 7d4d59ab5bcc61eaf2720f1715e4a8654e9ec37b41ed51ca9ce55a595076f478
Timestamp: 1743012050 Timestamp [UTC]: 2025-03-26 18:00:50 Age [y:d:h:m:s]: 01:047:14:05:42
Block: 1247836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284878 RingCT/type: yes/0
Extra: 017d4d59ab5bcc61eaf2720f1715e4a8654e9ec37b41ed51ca9ce55a595076f478021100000002d2e40efd000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c61cf11b01784fa905b828f9d34242b2185ccc961ac8a900c61d1d206402da0b 0.000600000000 1734863 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": 1247846, "vin": [ { "gen": { "height": 1247836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c61cf11b01784fa905b828f9d34242b2185ccc961ac8a900c61d1d206402da0b" } } ], "extra": [ 1, 125, 77, 89, 171, 91, 204, 97, 234, 242, 114, 15, 23, 21, 228, 168, 101, 78, 158, 195, 123, 65, 237, 81, 202, 156, 229, 90, 89, 80, 118, 244, 120, 2, 17, 0, 0, 0, 2, 210, 228, 14, 253, 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: