Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 130f4ef09e320234fa720ef0d387ea45013e7dce4fba9df17b03f73e44bd67a7

Tx prefix hash: 39fb1050976b3d999b9d065ae5f2979fbcd88757473e88c8cc60acac9a80f645
Tx public key: b84912013d9d5663310b019fd11bb435cd7f3c77ea0e5fb546c41295b483176d
Timestamp: 1760446827 Timestamp [UTC]: 2025-10-14 13:00:27 Age [y:d:h:m:s]: 01:028:16:14:15
Block: 1389762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286643 RingCT/type: yes/0
Extra: 01b84912013d9d5663310b019fd11bb435cd7f3c77ea0e5fb546c41295b483176d02110000000101491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 97554ce8a395ebfaf16eeaa06526d3cab06b1e8345590c230083f4b2d3bd94b6 0.000600000000 1877991 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": 1389772, "vin": [ { "gen": { "height": 1389762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97554ce8a395ebfaf16eeaa06526d3cab06b1e8345590c230083f4b2d3bd94b6" } } ], "extra": [ 1, 184, 73, 18, 1, 61, 157, 86, 99, 49, 11, 1, 159, 209, 27, 180, 53, 205, 127, 60, 119, 234, 14, 95, 181, 70, 196, 18, 149, 180, 131, 23, 109, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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: