Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0f91068118f7c329da9ed4affe0076b71d7ee0f74e98d55290398a478b6b9d2

Tx prefix hash: 90504acd6556e103f2ec9219036433ba5b4c4e154272a99a9ba095dc629c6b20
Tx public key: 784880471915613cc0da121c5bbdb575b158534542232e3b3690f673a69e579a
Timestamp: 1732702368 Timestamp [UTC]: 2024-11-27 10:12:48 Age [y:d:h:m:s]: 01:356:15:07:35
Block: 1162774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518758 RingCT/type: yes/0
Extra: 01784880471915613cc0da121c5bbdb575b158534542232e3b3690f673a69e579a021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7f337b8f74b6134c3966d23acf13a6a98b68a91aa7c9efc8d2e3740629a2abc3 0.000600000000 1648433 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": 1162784, "vin": [ { "gen": { "height": 1162774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f337b8f74b6134c3966d23acf13a6a98b68a91aa7c9efc8d2e3740629a2abc3" } } ], "extra": [ 1, 120, 72, 128, 71, 25, 21, 97, 60, 192, 218, 18, 28, 91, 189, 181, 117, 177, 88, 83, 69, 66, 35, 46, 59, 54, 144, 246, 115, 166, 158, 87, 154, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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: