Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b1565fd18b57f371ec45a4cd4756158fd5d386fcee75cac7568fa74aaeac1f7

Tx prefix hash: 642b6784fef28ed095e71c1135612c719fa5a5e8fe9ec3dcdee0f6fdeecb5294
Tx public key: a226ea64f203ffe42ec7fa00ba85367b7cf7a275a2c2dff5f7a4a155a37b47e6
Timestamp: 1620579385 Timestamp [UTC]: 2021-05-09 16:56:25 Age [y:d:h:m:s]: 05:012:00:44:13
Block: 257543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1281606 RingCT/type: yes/0
Extra: 01a226ea64f203ffe42ec7fa00ba85367b7cf7a275a2c2dff5f7a4a155a37b47e602110000005c5ecf8729000000000000000000

1 output(s) for total of 0.086030744501 xmr

stealth address amount amount idx tag
00: 986ec148905ae2a44143ac08323d3991848d8753935b3696e51c79831a7e8eeb 0.086030744501 542172 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": 257553, "vin": [ { "gen": { "height": 257543 } } ], "vout": [ { "amount": 86030744501, "target": { "key": "986ec148905ae2a44143ac08323d3991848d8753935b3696e51c79831a7e8eeb" } } ], "extra": [ 1, 162, 38, 234, 100, 242, 3, 255, 228, 46, 199, 250, 0, 186, 133, 54, 123, 124, 247, 162, 117, 162, 194, 223, 245, 247, 164, 161, 85, 163, 123, 71, 230, 2, 17, 0, 0, 0, 92, 94, 207, 135, 41, 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: