Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78c4a7983f0a94f16fae6ea4ecdbcd1320a208821ef2d14cf3d4c1a0fe7d7da3

Tx prefix hash: c9b7079cec9f73ad19c1a798c94658b9ffa3885ddfbdf5b944806999259146ba
Tx public key: 8edffda8fd59c863c4d39c3b042e0c58e76bcbcc9167722b0ac4826c881f83cf
Timestamp: 1769477025 Timestamp [UTC]: 2026-01-27 01:23:45 Age [y:d:h:m:s]: 00:290:06:37:30
Block: 1464415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212834 RingCT/type: yes/0
Extra: 018edffda8fd59c863c4d39c3b042e0c58e76bcbcc9167722b0ac4826c881f83cf021100000004215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ae7d4b9b4a9aa4472f6d77c3ae458ee9b155d1add8a376f25a6f582788301ab5 0.000600000000 1953641 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": 1464425, "vin": [ { "gen": { "height": 1464415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae7d4b9b4a9aa4472f6d77c3ae458ee9b155d1add8a376f25a6f582788301ab5" } } ], "extra": [ 1, 142, 223, 253, 168, 253, 89, 200, 99, 196, 211, 156, 59, 4, 46, 12, 88, 231, 107, 203, 204, 145, 103, 114, 43, 10, 196, 130, 108, 136, 31, 131, 207, 2, 17, 0, 0, 0, 4, 33, 91, 191, 137, 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: