Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b50eaf4242ce9998a6c500ed5a845e2ebcfcd5458b3b058224be321a76c5ae70

Tx prefix hash: 00d7252f1a0b71e1a4c0cd06e12b030deba8e4b1fa82cc17fc26fb1a7e3b3344
Tx public key: 2973ea6e66234164d0f1a5b9358488a81dbb2ec7a2995451cf97bcc8d9a7107e
Timestamp: 1760673843 Timestamp [UTC]: 2025-10-17 04:04:03 Age [y:d:h:m:s]: 01:033:01:10:19
Block: 1391647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290012 RingCT/type: yes/0
Extra: 012973ea6e66234164d0f1a5b9358488a81dbb2ec7a2995451cf97bcc8d9a7107e02110000000225a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 36e5a6d546a4de3068360a5dc3d1770ef752c7d6202f50fe5ee7e5f17868a971 0.000600000000 1879894 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": 1391657, "vin": [ { "gen": { "height": 1391647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36e5a6d546a4de3068360a5dc3d1770ef752c7d6202f50fe5ee7e5f17868a971" } } ], "extra": [ 1, 41, 115, 234, 110, 102, 35, 65, 100, 208, 241, 165, 185, 53, 132, 136, 168, 29, 187, 46, 199, 162, 153, 84, 81, 207, 151, 188, 200, 217, 167, 16, 126, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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: