Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d044986352534e1cfb8bcbf2f79e26d7226c09c5f9f3130900bcdafaf37702e0

Tx prefix hash: ec2e08158640e4b060b5f173fb42da85e23401e57bb0179e0ca0ea9b5d5c9c40
Tx public key: 820fca4710d1df8f158ea78ca6c0ed667a065d31b281c68eef08314e86c7fb97
Timestamp: 1772484872 Timestamp [UTC]: 2026-03-02 20:54:32 Age [y:d:h:m:s]: 00:264:21:28:03
Block: 1489311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194183 RingCT/type: yes/0
Extra: 01820fca4710d1df8f158ea78ca6c0ed667a065d31b281c68eef08314e86c7fb97021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 070b3ca496e2761b0916e3ad0b3e9021ae2405e453d5f9b3e661660e028700ba 0.000600000000 1978801 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": 1489321, "vin": [ { "gen": { "height": 1489311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "070b3ca496e2761b0916e3ad0b3e9021ae2405e453d5f9b3e661660e028700ba" } } ], "extra": [ 1, 130, 15, 202, 71, 16, 209, 223, 143, 21, 142, 167, 140, 166, 192, 237, 102, 122, 6, 93, 49, 178, 129, 198, 142, 239, 8, 49, 78, 134, 199, 251, 151, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: