Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd5c6da4e75d82a102d943308f071207ba7bce4d8912af6f7c72def28f33903e

Tx prefix hash: 27b1f5959ce9ae919f450430a6c9e0abecc41b6654839dcc6dbcbec5a5b07cd1
Tx public key: e00fe9b7c5748d0f533e363d2b6618da37d470c0bcb533ed390e02d90d6d05e6
Timestamp: 1683650534 Timestamp [UTC]: 2023-05-09 16:42:14 Age [y:d:h:m:s]: 03:195:16:59:38
Block: 756464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 926129 RingCT/type: yes/0
Extra: 01e00fe9b7c5748d0f533e363d2b6618da37d470c0bcb533ed390e02d90d6d05e602110000000633af99f4000000000000000000

1 output(s) for total of 0.001912145512 xmr

stealth address amount amount idx tag
00: 29be079366321229671252b80c587557c1ac8ba4229ab3e95429c3c484f44759 0.001912145512 1204843 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": 756474, "vin": [ { "gen": { "height": 756464 } } ], "vout": [ { "amount": 1912145512, "target": { "key": "29be079366321229671252b80c587557c1ac8ba4229ab3e95429c3c484f44759" } } ], "extra": [ 1, 224, 15, 233, 183, 197, 116, 141, 15, 83, 62, 54, 61, 43, 102, 24, 218, 55, 212, 112, 192, 188, 181, 51, 237, 57, 14, 2, 217, 13, 109, 5, 230, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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: