Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2a0e4c47d366b3bc86c270889697d7877f92f7d0ba59fc25f3dad6bf5ac367e

Tx prefix hash: 9fb81c4c904621f3eafa5e64d92e05bda437e9444033fa80b90f74b3e03f107c
Tx public key: dd87f6fd761fa310bf2e6194a2f74be4a9915c407848c5e9efdaf30d6d17d2e7
Timestamp: 1771542346 Timestamp [UTC]: 2026-02-19 23:05:46 Age [y:d:h:m:s]: 00:271:11:49:43
Block: 1481519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199563 RingCT/type: yes/0
Extra: 01dd87f6fd761fa310bf2e6194a2f74be4a9915c407848c5e9efdaf30d6d17d2e7021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 49662e99b5f8ce0931a8f3c22ee654a54646f3ca294b268fa8469438b155c5f2 0.000600000000 1970901 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": 1481529, "vin": [ { "gen": { "height": 1481519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49662e99b5f8ce0931a8f3c22ee654a54646f3ca294b268fa8469438b155c5f2" } } ], "extra": [ 1, 221, 135, 246, 253, 118, 31, 163, 16, 191, 46, 97, 148, 162, 247, 75, 228, 169, 145, 92, 64, 120, 72, 197, 233, 239, 218, 243, 13, 109, 23, 210, 231, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: