Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b9657a97ff4bd9a895dd65f31c1acd315e9344f9d8a56bc7bc82fdc08755da6

Tx prefix hash: 222f3345883da204886e9da7469bb705a6a87ca560d6048ed41e01a6849c7e01
Tx public key: 88f4c8b40967bfd9df380ee5f79818f88af65e7a9a7f27c3712340b91e664c3a
Timestamp: 1692767049 Timestamp [UTC]: 2023-08-23 05:04:09 Age [y:d:h:m:s]: 02:268:20:18:34
Block: 831950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 704346 RingCT/type: yes/0
Extra: 0188f4c8b40967bfd9df380ee5f79818f88af65e7a9a7f27c3712340b91e664c3a021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.001074989876 xmr

stealth address amount amount idx tag
00: a43daa4b085f1373985aa85c654808b11efe1356f1dceaead0a4eaae6ee54936 0.001074989876 1284380 of 0 -

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": 831960, "vin": [ { "gen": { "height": 831950 } } ], "vout": [ { "amount": 1074989876, "target": { "key": "a43daa4b085f1373985aa85c654808b11efe1356f1dceaead0a4eaae6ee54936" } } ], "extra": [ 1, 136, 244, 200, 180, 9, 103, 191, 217, 223, 56, 14, 229, 247, 152, 24, 248, 138, 246, 94, 122, 154, 127, 39, 195, 113, 35, 64, 185, 30, 102, 76, 58, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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: