Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ef4fc3b85100524f441d19d64c2212f42e40431f085b249357d16ba2b8444f0

Tx prefix hash: f22b44ad236e88a551c25a42ab0d08f043f5104cb297f793a9e183e9f09486b3
Tx public key: eacf081e65cc010eab507a70658b2cc7db27250ced7f88755a99aec217867c6d
Timestamp: 1758822871 Timestamp [UTC]: 2025-09-25 17:54:31 Age [y:d:h:m:s]: 01:049:03:37:52
Block: 1376312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301360 RingCT/type: yes/0
Extra: 01eacf081e65cc010eab507a70658b2cc7db27250ced7f88755a99aec217867c6d02110000000125a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f781f164e4e30d09eaa95902780a38a5cd6b257b45321bb6e0d9182324a5dcc1 0.000600000000 1864403 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": 1376322, "vin": [ { "gen": { "height": 1376312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f781f164e4e30d09eaa95902780a38a5cd6b257b45321bb6e0d9182324a5dcc1" } } ], "extra": [ 1, 234, 207, 8, 30, 101, 204, 1, 14, 171, 80, 122, 112, 101, 139, 44, 199, 219, 39, 37, 12, 237, 127, 136, 117, 90, 153, 174, 194, 23, 134, 124, 109, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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: