Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f90b9053bdbd42b7b0aa7cc34726cfabfe2c3adad7f663c079e722371b85fc2a

Tx prefix hash: 37d332696ef9e59efe588a8b9d501fcd886b52a6d46a73d503247a5e2409f556
Tx public key: 3a39e89a45b1328f28deed69495b766d84cbd88d37b5d2d52fce712883a17503
Timestamp: 1764810159 Timestamp [UTC]: 2025-12-04 01:02:39 Age [y:d:h:m:s]: 00:346:01:02:16
Block: 1425921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252635 RingCT/type: yes/0
Extra: 013a39e89a45b1328f28deed69495b766d84cbd88d37b5d2d52fce712883a1750302110000000270609d03000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 19c58ef36405e4ea9f5e4976d4d9d5423445b243c4dafa97841fe95c5a79da4a 0.000600000000 1914604 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": 1425931, "vin": [ { "gen": { "height": 1425921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19c58ef36405e4ea9f5e4976d4d9d5423445b243c4dafa97841fe95c5a79da4a" } } ], "extra": [ 1, 58, 57, 232, 154, 69, 177, 50, 143, 40, 222, 237, 105, 73, 91, 118, 109, 132, 203, 216, 141, 55, 181, 210, 213, 47, 206, 113, 40, 131, 161, 117, 3, 2, 17, 0, 0, 0, 2, 112, 96, 157, 3, 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: