Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44b47b54c6c09c9c9dcd5d7cc014589f804aa8d80c67da24608845ed72a1b09c

Tx prefix hash: a5975385db2b1ceb874bb6331833f07abb9ae15818561e290ce75448b96a98cf
Tx public key: 0ad60b0ca948d4d658179a99b369b1a24262db51b6f8cc2969f07703a8558dba
Timestamp: 1723380123 Timestamp [UTC]: 2024-08-11 12:42:03 Age [y:d:h:m:s]: 01:282:02:05:42
Block: 1085582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453481 RingCT/type: yes/0
Extra: 010ad60b0ca948d4d658179a99b369b1a24262db51b6f8cc2969f07703a8558dba02110000000de914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b450cf48ec8aa0dcd095f92ff5b378a4cc1f1a3881c758f56f722d0336887ba7 0.000600000000 1560169 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": 1085592, "vin": [ { "gen": { "height": 1085582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b450cf48ec8aa0dcd095f92ff5b378a4cc1f1a3881c758f56f722d0336887ba7" } } ], "extra": [ 1, 10, 214, 11, 12, 169, 72, 212, 214, 88, 23, 154, 153, 179, 105, 177, 162, 66, 98, 219, 81, 182, 248, 204, 41, 105, 240, 119, 3, 168, 85, 141, 186, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 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: