Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fb84871f7bd6c9fdb612164cb9d62b3ccf850f6fe3d29efad4ec564241e522c

Tx prefix hash: f32016460eb395c0fdc1e2100d70e7a0724cab734b4ab40a6a3b0f5e284db18f
Tx public key: 6cb56fe33b0b6ce347ae5a159c801cea8b2e72155b8997c5c7ecb76e909f4470
Timestamp: 1771762087 Timestamp [UTC]: 2026-02-22 12:08:07 Age [y:d:h:m:s]: 00:269:20:41:51
Block: 1483338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198431 RingCT/type: yes/0
Extra: 016cb56fe33b0b6ce347ae5a159c801cea8b2e72155b8997c5c7ecb76e909f4470021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 667594b00f5039c7c27aaa612943b68ca2deba08d6e11053c7a857d1acd8fcce 0.000600000000 1972744 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": 1483348, "vin": [ { "gen": { "height": 1483338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "667594b00f5039c7c27aaa612943b68ca2deba08d6e11053c7a857d1acd8fcce" } } ], "extra": [ 1, 108, 181, 111, 227, 59, 11, 108, 227, 71, 174, 90, 21, 156, 128, 28, 234, 139, 46, 114, 21, 91, 137, 151, 197, 199, 236, 183, 110, 144, 159, 68, 112, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: