Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa98e04d1688400087de5970b9d9fa6cda3151a48961b71e407ea3f8c090872e

Tx prefix hash: 98798a065a9785b5229570f42ff04349ca5e6f02ef655d734aaa5592c9e8e87d
Tx public key: 35a96848542babf8af8746642849c2b191fa244e4c326b5ce19bfc0a75a28fdd
Timestamp: 1708194491 Timestamp [UTC]: 2024-02-17 18:28:11 Age [y:d:h:m:s]: 02:278:11:37:12
Block: 959679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 723815 RingCT/type: yes/0
Extra: 0135a96848542babf8af8746642849c2b191fa244e4c326b5ce19bfc0a75a28fdd0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bb07351490526c331aba14f76bea63cfe9cf964a9b07566f9c424235afc37cc3 0.000600000000 1419232 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": 959689, "vin": [ { "gen": { "height": 959679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb07351490526c331aba14f76bea63cfe9cf964a9b07566f9c424235afc37cc3" } } ], "extra": [ 1, 53, 169, 104, 72, 84, 43, 171, 248, 175, 135, 70, 100, 40, 73, 194, 177, 145, 250, 36, 78, 76, 50, 107, 92, 225, 155, 252, 10, 117, 162, 143, 221, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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: