Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: affbcda522465a4c22cfc4bfebbcc9fee1afdbced79c36e45ac452240dbccebd

Tx prefix hash: 3347a8fc731eebc4cd0982c39c81d1fe66516bad596721fca5f8c3a30ea21402
Tx public key: 62b7ce9f319b5d12939f5c5d1179221a2545087495aebbcbb11e713c0a978587
Timestamp: 1748932996 Timestamp [UTC]: 2025-06-03 06:43:16 Age [y:d:h:m:s]: 01:163:23:44:10
Block: 1296888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381065 RingCT/type: yes/0
Extra: 0162b7ce9f319b5d12939f5c5d1179221a2545087495aebbcbb11e713c0a978587021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 44f4636e2b7a5d62e4df17b49a64f3341f311397b9fe3f0fa3688f6dd473e439 0.000600000000 1784405 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": 1296898, "vin": [ { "gen": { "height": 1296888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44f4636e2b7a5d62e4df17b49a64f3341f311397b9fe3f0fa3688f6dd473e439" } } ], "extra": [ 1, 98, 183, 206, 159, 49, 155, 93, 18, 147, 159, 92, 93, 17, 121, 34, 26, 37, 69, 8, 116, 149, 174, 187, 203, 177, 30, 113, 60, 10, 151, 133, 135, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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: