Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e53f3656ded1ae5fea0a764df37a3a631401b8c1fef81b01a5a9f6788cb0e57f

Tx prefix hash: 35dc1e19f76ecbe0ae9d7d06b6ee2bcb73def98125de517e71500d4a258d7f64
Tx public key: 1d02368d7d20b35d5899276efff8add95fefc7673405c80053bb5da39a8490d7
Timestamp: 1774945747 Timestamp [UTC]: 2026-03-31 08:29:07 Age [y:d:h:m:s]: 00:233:12:21:16
Block: 1509673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172476 RingCT/type: yes/0
Extra: 011d02368d7d20b35d5899276efff8add95fefc7673405c80053bb5da39a8490d7021100000003ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fb8bcf07b1236008bf02dc7baea81f73cf0a3c02c3df2a871b1f1a4a540953fb 0.000600000000 1999449 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": 1509683, "vin": [ { "gen": { "height": 1509673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb8bcf07b1236008bf02dc7baea81f73cf0a3c02c3df2a871b1f1a4a540953fb" } } ], "extra": [ 1, 29, 2, 54, 141, 125, 32, 179, 93, 88, 153, 39, 110, 255, 248, 173, 217, 95, 239, 199, 103, 52, 5, 200, 0, 83, 187, 93, 163, 154, 132, 144, 215, 2, 17, 0, 0, 0, 3, 238, 75, 113, 129, 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: