Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdd44990015f14daf54cc6a6e86af5da71da00ef867a074fc07dae7b2b023f32

Tx prefix hash: 4ee4e1bd05ccfc6c3f9460da2ba83e90280b47e0455cc4b523819cbb264b0c16
Tx public key: 009c25a39625c2419f631e1a394e40509c0553e0a6783a6d36a530c3b59ae53b
Timestamp: 1742036119 Timestamp [UTC]: 2025-03-15 10:55:19 Age [y:d:h:m:s]: 01:249:18:15:15
Block: 1239797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442622 RingCT/type: yes/0
Extra: 01009c25a39625c2419f631e1a394e40509c0553e0a6783a6d36a530c3b59ae53b021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bb39ae704872d3fe4d952219718c9ec482706e21dcb61631330f3bbe04bbd9e1 0.000600000000 1726762 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": 1239807, "vin": [ { "gen": { "height": 1239797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb39ae704872d3fe4d952219718c9ec482706e21dcb61631330f3bbe04bbd9e1" } } ], "extra": [ 1, 0, 156, 37, 163, 150, 37, 194, 65, 159, 99, 30, 26, 57, 78, 64, 80, 156, 5, 83, 224, 166, 120, 58, 109, 54, 165, 48, 195, 181, 154, 229, 59, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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: