Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd5e43bdfd24c9f0060d26998f99314b8807f82e17a79318049e5f383a3321c8

Tx prefix hash: 0ef596a329ab1403efde5caecfa7bbc1c4979f3c6b020ad6e360229167854ede
Tx public key: ada313cd3525ef3b145543eccfa841dafa08092e603bb5f720dc61d03e7b1b80
Timestamp: 1745474019 Timestamp [UTC]: 2025-04-24 05:53:39 Age [y:d:h:m:s]: 01:015:19:12:35
Block: 1268229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262510 RingCT/type: yes/0
Extra: 01ada313cd3525ef3b145543eccfa841dafa08092e603bb5f720dc61d03e7b1b800211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b3e599a4364912c9e17e85f833992a00cc79fe35da80d467c1724c18b3cadf8d 0.000600000000 1755458 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": 1268239, "vin": [ { "gen": { "height": 1268229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3e599a4364912c9e17e85f833992a00cc79fe35da80d467c1724c18b3cadf8d" } } ], "extra": [ 1, 173, 163, 19, 205, 53, 37, 239, 59, 20, 85, 67, 236, 207, 168, 65, 218, 250, 8, 9, 46, 96, 59, 181, 247, 32, 220, 97, 208, 62, 123, 27, 128, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: