Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3006b21b4660f38cdf7d35acfe52b76debe7cf007cf8fc7407190b6ad89aa960

Tx prefix hash: 3d8bde007729752c9af2892585b22ecff8c123a135b47f71080282c1e3a6dac9
Tx public key: f22b6bedd05a8bb1e6480ce88bc9ee8f945e0f7232f2ead813b6731919b4e934
Timestamp: 1744061223 Timestamp [UTC]: 2025-04-07 21:27:03 Age [y:d:h:m:s]: 01:039:05:56:55
Block: 1256522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279044 RingCT/type: yes/0
Extra: 01f22b6bedd05a8bb1e6480ce88bc9ee8f945e0f7232f2ead813b6731919b4e93402110000000101491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ba3f01c5a38f1e4503b2153b7e36efccfe2eaa677cba90ef7e197a494f8b03ed 0.000600000000 1743637 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": 1256532, "vin": [ { "gen": { "height": 1256522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba3f01c5a38f1e4503b2153b7e36efccfe2eaa677cba90ef7e197a494f8b03ed" } } ], "extra": [ 1, 242, 43, 107, 237, 208, 90, 139, 177, 230, 72, 12, 232, 139, 201, 238, 143, 148, 94, 15, 114, 50, 242, 234, 216, 19, 182, 115, 25, 25, 180, 233, 52, 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: