Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 310110c45314694cb58567965c7c323d8a88540651994b7db7830928ee4a67a4

Tx prefix hash: c032174aff7a238edea7f06c6b80c186cbbcdd886f90528b4e8a5b87d53f8eac
Tx public key: 1cd8bafe54acaea3a1309b95cde3be02258564fa7f4cbf7c12c86b4c3b9d74b8
Timestamp: 1722530510 Timestamp [UCT]: 2024-08-01 16:41:50 Age [y:d:h:m:s]: 00:268:20:42:31
Block: 1078536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192074 RingCT/type: yes/0
Extra: 011cd8bafe54acaea3a1309b95cde3be02258564fa7f4cbf7c12c86b4c3b9d74b802110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a66742a3f78a62dfdaba80a680ac15019fb60b5de37f96a87fb09ab8fc687852 0.600000000000 1551121 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 dinasty-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": 1078546, "vin": [ { "gen": { "height": 1078536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a66742a3f78a62dfdaba80a680ac15019fb60b5de37f96a87fb09ab8fc687852" } } ], "extra": [ 1, 28, 216, 186, 254, 84, 172, 174, 163, 161, 48, 155, 149, 205, 227, 190, 2, 37, 133, 100, 250, 127, 76, 191, 124, 18, 200, 107, 76, 59, 157, 116, 184, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8