Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7ee99bd5b9c290ec07d02527320c59f3660056c1e5db621b044ec2d0e3d2847

Tx prefix hash: 2ed230936bfaf234093614909b7085951643e94383056bb6b24198a4caf580b0
Tx public key: 88a3de44058803a04d747549cc64357e4fdc38f008473c77a8b2775b302f87b9
Timestamp: 1775163704 Timestamp [UTC]: 2026-04-02 21:01:44 Age [y:d:h:m:s]: 00:233:06:00:39
Block: 1511478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172016 RingCT/type: yes/0
Extra: 0188a3de44058803a04d747549cc64357e4fdc38f008473c77a8b2775b302f87b902110000000243b50471000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9e6a4e9864d1972237239d4288eaed3c3f0aa5459d820d55dcc39e052c6137fc 0.000600000000 2001270 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": 1511488, "vin": [ { "gen": { "height": 1511478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e6a4e9864d1972237239d4288eaed3c3f0aa5459d820d55dcc39e052c6137fc" } } ], "extra": [ 1, 136, 163, 222, 68, 5, 136, 3, 160, 77, 116, 117, 73, 204, 100, 53, 126, 79, 220, 56, 240, 8, 71, 60, 119, 168, 178, 119, 91, 48, 47, 135, 185, 2, 17, 0, 0, 0, 2, 67, 181, 4, 113, 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: