Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 334cb7e75d8510af45bab0b805148b935b27df54fa88b3a20c0de66fa559cd53

Tx prefix hash: 7c7804db3696415bc02254adbe7256758522e5de82e17e6f8484fd1ca3d86b20
Tx public key: dd7cbee58137080c982a74e4212bcc2d07f4e1ad93a29aea97e474427596feb9
Timestamp: 1773085236 Timestamp [UTC]: 2026-03-09 19:40:36 Age [y:d:h:m:s]: 00:167:01:31:21
Block: 1494278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125203 RingCT/type: yes/0
Extra: 01dd7cbee58137080c982a74e4212bcc2d07f4e1ad93a29aea97e474427596feb9021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 847589f922fbf21591632bbb78761b4d63d695a2eafdc73bf39ff750ed3473a9 0.000600000000 1983848 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": 1494288, "vin": [ { "gen": { "height": 1494278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "847589f922fbf21591632bbb78761b4d63d695a2eafdc73bf39ff750ed3473a9" } } ], "extra": [ 1, 221, 124, 190, 229, 129, 55, 8, 12, 152, 42, 116, 228, 33, 43, 204, 45, 7, 244, 225, 173, 147, 162, 154, 234, 151, 228, 116, 66, 117, 150, 254, 185, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: