Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41aeeab5c0e883e4cbc704a3a7bec76a8dbf21ea24a171550337a709c56a4167

Tx prefix hash: 636f0073e35f985ab3cd91460342f0756d5fa1f4618f38123e020f341e083cc7
Tx public key: 4c8847e85f8833f7e501f312342061dec3878b6ecd30ac5596c3fe847b451350
Timestamp: 1722655783 Timestamp [UTC]: 2024-08-03 03:29:43 Age [y:d:h:m:s]: 02:108:06:50:40
Block: 1079580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 602232 RingCT/type: yes/0
Extra: 014c8847e85f8833f7e501f312342061dec3878b6ecd30ac5596c3fe847b45135002110000000bdaef6b5b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 570a3ed71a2d9389fd01c33a08acc8f7d9b9b25fd7785d11628d456b27788dc1 0.000600000000 1552593 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": 1079590, "vin": [ { "gen": { "height": 1079580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "570a3ed71a2d9389fd01c33a08acc8f7d9b9b25fd7785d11628d456b27788dc1" } } ], "extra": [ 1, 76, 136, 71, 232, 95, 136, 51, 247, 229, 1, 243, 18, 52, 32, 97, 222, 195, 135, 139, 110, 205, 48, 172, 85, 150, 195, 254, 132, 123, 69, 19, 80, 2, 17, 0, 0, 0, 11, 218, 239, 107, 91, 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: