Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc5dbe5afeb19ace572098bc8a2c1bef177094e228ab37443aab302f0eb9c734

Tx prefix hash: c51baf3ad5d22d53a2d6d4b69e1b96a6cf9aa2836be819f0c552b51769e422d9
Tx public key: 140f26dcf66a1be8151855ebc97c3068d281a844756493a79ce8efcbcbeb0f75
Timestamp: 1647295799 Timestamp [UTC]: 2022-03-14 22:09:59 Age [y:d:h:m:s]: 04:254:01:38:03
Block: 458525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1225625 RingCT/type: yes/0
Extra: 01140f26dcf66a1be8151855ebc97c3068d281a844756493a79ce8efcbcbeb0f75021100000009cb8520c2000000000000000000

1 output(s) for total of 0.018565925290 xmr

stealth address amount amount idx tag
00: 64dfaaab14a85fb30c7a2e88c642830d6685fe4be4b5d4ac4a257f743cd173a4 0.018565925290 875046 of 0 -

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": 458535, "vin": [ { "gen": { "height": 458525 } } ], "vout": [ { "amount": 18565925290, "target": { "key": "64dfaaab14a85fb30c7a2e88c642830d6685fe4be4b5d4ac4a257f743cd173a4" } } ], "extra": [ 1, 20, 15, 38, 220, 246, 106, 27, 232, 21, 24, 85, 235, 201, 124, 48, 104, 210, 129, 168, 68, 117, 100, 147, 167, 156, 232, 239, 203, 203, 235, 15, 117, 2, 17, 0, 0, 0, 9, 203, 133, 32, 194, 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: