Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d76a0f6ada6c8a92caef312dc2bd8c6ec4fd78060327296e9db45902d7770149

Tx prefix hash: c7de0e25e2740aa37c9ce4f204e471cb7c4000acc20cd374e15a77cdde1a4d28
Tx public key: fbac1c16f14569c971a2960dfb974ce9eb3e54f9d30fa2c3464a77454004e525
Timestamp: 1760284455 Timestamp [UTC]: 2025-10-12 15:54:15 Age [y:d:h:m:s]: 01:038:11:50:07
Block: 1388417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293958 RingCT/type: yes/0
Extra: 01fbac1c16f14569c971a2960dfb974ce9eb3e54f9d30fa2c3464a77454004e525021100000002719c6d43000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5064e81d44e46ff522686fe8b49d8dc20f2e5d04dfb905e26f6e93bdef339b04 0.000600000000 1876626 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": 1388427, "vin": [ { "gen": { "height": 1388417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5064e81d44e46ff522686fe8b49d8dc20f2e5d04dfb905e26f6e93bdef339b04" } } ], "extra": [ 1, 251, 172, 28, 22, 241, 69, 105, 201, 113, 162, 150, 13, 251, 151, 76, 233, 235, 62, 84, 249, 211, 15, 162, 195, 70, 74, 119, 69, 64, 4, 229, 37, 2, 17, 0, 0, 0, 2, 113, 156, 109, 67, 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: