Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5ac1dfbe7f13fe5ec569f2f1bd8df0fcc257ff8089400b9b7ef1b9335852aff

Tx prefix hash: 47e3df99084224d34addb43afad8016df9cc0ea129d0ae0fa9623baabab4e8fd
Tx public key: 27a74f071e17ebf935b5aeef6da69ac19ce544abeae277750e7f6d89bea0cde5
Timestamp: 1675579348 Timestamp [UTC]: 2023-02-05 06:42:28 Age [y:d:h:m:s]: 03:097:12:53:58
Block: 690164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 842162 RingCT/type: yes/0
Extra: 0127a74f071e17ebf935b5aeef6da69ac19ce544abeae277750e7f6d89bea0cde50211000000025029cbac000000000000000000

1 output(s) for total of 0.003171028132 xmr

stealth address amount amount idx tag
00: e909f3ea2239fa1733a9356b91dfadd6e2d9f9c33d2a4bbf9a223de64850e448 0.003171028132 1132874 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": 690174, "vin": [ { "gen": { "height": 690164 } } ], "vout": [ { "amount": 3171028132, "target": { "key": "e909f3ea2239fa1733a9356b91dfadd6e2d9f9c33d2a4bbf9a223de64850e448" } } ], "extra": [ 1, 39, 167, 79, 7, 30, 23, 235, 249, 53, 181, 174, 239, 109, 166, 154, 193, 156, 229, 68, 171, 234, 226, 119, 117, 14, 127, 109, 137, 190, 160, 205, 229, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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: