Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47ecdfd7830059dd8b69e94784f95aa9be11a124ef34737233ba70181ae9d179

Tx prefix hash: 7385cdacb1fa070864b0b39d64408b2282d5453c67d893c7cdbdc9b34cc0fd7a
Tx public key: 0163850d0ea2c0d30b4e98802f2e6b053bdd60c1fb36d4aa3902173411a330e8
Timestamp: 1780524254 Timestamp [UTC]: 2026-06-03 22:04:14 Age [y:d:h:m:s]: 00:171:15:40:36
Block: 1550549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 132945 RingCT/type: yes/0
Extra: 010163850d0ea2c0d30b4e98802f2e6b053bdd60c1fb36d4aa3902173411a330e8

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 737a4b7b01736f24c47db9c81e7a83739265beaab4b4f845458cbe41724790b7 0.000600000000 2040523 of 15 <39>

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": 1550559, "vin": [ { "gen": { "height": 1550549 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "737a4b7b01736f24c47db9c81e7a83739265beaab4b4f845458cbe41724790b7", "view_tag": "39" } } } ], "extra": [ 1, 1, 99, 133, 13, 14, 162, 192, 211, 11, 78, 152, 128, 47, 46, 107, 5, 59, 221, 96, 193, 251, 54, 212, 170, 57, 2, 23, 52, 17, 163, 48, 232 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: