Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 882935cf48978b922afc45d31dc1ed99eba02ebc5bdadfef56eebce7099974f6

Tx prefix hash: cff1d4d541310bd55502436e98bd0bc83c5dd46c24d2abdc0d9dc5c18eb060c6
Tx public key: b1d3ac7fa7812d2bfc20a22356b07f5b497fd45541efb3b74da1f8d10bc5f951
Timestamp: 1736583727 Timestamp [UTC]: 2025-01-11 08:22:07 Age [y:d:h:m:s]: 01:315:01:55:53
Block: 1194904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488590 RingCT/type: yes/0
Extra: 01b1d3ac7fa7812d2bfc20a22356b07f5b497fd45541efb3b74da1f8d10bc5f9510211000000031f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 780e4f1128fff34c5a2321da2728c6ae6fa67b0da81787f23cf89f6abd040042 0.000600000000 1681483 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": 1194914, "vin": [ { "gen": { "height": 1194904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "780e4f1128fff34c5a2321da2728c6ae6fa67b0da81787f23cf89f6abd040042" } } ], "extra": [ 1, 177, 211, 172, 127, 167, 129, 45, 43, 252, 32, 162, 35, 86, 176, 127, 91, 73, 127, 212, 85, 65, 239, 179, 183, 77, 161, 248, 209, 11, 197, 249, 81, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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: